From: patchwork-bot+netdevbpf@kernel.org
To: Grant Grundler <grundler@chromium.org>
Cc: linux@rempel-privat.de, paskripkin@gmail.com, lukas@wunner.de,
eizan@chromium.org, kuba@kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
glance@acc.umu.se
Subject: Re: [PATCHv6 net] net: asix: fix modprobe "sysfs: cannot create duplicate filename"
Date: Thu, 23 Mar 2023 05:10:17 +0000 [thread overview]
Message-ID: <167954821780.28676.14135490297791050064.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230321170539.732147-1-grundler@chromium.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 21 Mar 2023 10:05:39 -0700 you wrote:
> "modprobe asix ; rmmod asix ; modprobe asix" fails with:
> sysfs: cannot create duplicate filename \
> '/devices/virtual/mdio_bus/usb-003:004'
>
> Issue was originally reported by Anton Lundin on 2022-06-22 (link below).
>
> Chrome OS team hit the same issue in Feb, 2023 when trying to find
> work arounds for other issues with AX88172 devices.
>
> [...]
Here is the summary with links:
- [PATCHv6,net] net: asix: fix modprobe "sysfs: cannot create duplicate filename"
https://git.kernel.org/netdev/net/c/8eac0095de35
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-23 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 17:05 [PATCHv6 net] net: asix: fix modprobe "sysfs: cannot create duplicate filename" Grant Grundler
2023-03-23 5:10 ` patchwork-bot+netdevbpf [this message]
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=167954821780.28676.14135490297791050064.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=eizan@chromium.org \
--cc=glance@acc.umu.se \
--cc=grundler@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
/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