From: patchwork-bot+netdevbpf@kernel.org
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, jarkko.palviainen@gmail.com
Subject: Re: [PATCH v2] net: usb: ax88179_178a: avoid writing the mac address before first reading
Date: Thu, 18 Apr 2024 17:00:27 +0000 [thread overview]
Message-ID: <171345962745.29083.15641493659556059187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240417085524.219532-1-jtornosm@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 17 Apr 2024 10:55:13 +0200 you wrote:
> After the commit d2689b6a86b9 ("net: usb: ax88179_178a: avoid two
> consecutive device resets"), reset operation, in which the default mac
> address from the device is read, is not executed from bind operation and
> the random address, that is pregenerated just in case, is direclty written
> the first time in the device, so the default one from the device is not
> even read. This writing is not dangerous because is volatile and the
> default mac address is not missed.
>
> [...]
Here is the summary with links:
- [v2] net: usb: ax88179_178a: avoid writing the mac address before first reading
https://git.kernel.org/netdev/net/c/56f78615bcb1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-04-18 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:55 [PATCH v2] net: usb: ax88179_178a: avoid writing the mac address before first reading Jose Ignacio Tornos Martinez
2024-04-18 17:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 23:16 Isaac Ganoung
2024-04-30 15:27 ` Jakub Kicinski
2024-04-30 16:00 ` Jose Ignacio Tornos Martinez
2024-05-08 5:42 ` Yongqin Liu
2024-05-08 7:56 ` Jose Ignacio Tornos Martinez
2024-05-08 10:41 ` Yongqin Liu
2024-05-14 6:29 ` Yongqin Liu
2024-05-14 7:00 ` Jose Ignacio Tornos Martinez
2024-05-14 9:14 ` Yongqin Liu
2024-05-23 4:17 ` Yongqin Liu
2024-05-09 21:09 Jeffery Miller
2024-05-10 6:08 ` Jose Ignacio Tornos Martinez
2024-05-23 22:27 ` Jeffery Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171345962745.29083.15641493659556059187.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jarkko.palviainen@gmail.com \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).