From: patchwork-bot+netdevbpf@kernel.org
To: Fabio Estevam <festevam@gmail.com>
Cc: kuba@kernel.org, steve.glendinning@shawell.net,
UNGLinuxDriver@microchip.com, fntoth@gmail.com,
martyn.welch@collabora.com, andrew@lunn.ch,
netdev@vger.kernel.org, linux-usb@vger.kernel.org, marex@denx.de,
festevam@denx.de
Subject: Re: [PATCH v2 net] smsc95xx: Ignore -ENODEV errors when device is unplugged
Date: Mon, 07 Mar 2022 12:40:11 +0000 [thread overview]
Message-ID: <164665681144.14619.4945223702291737274.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220305204720.2978554-1-festevam@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 5 Mar 2022 17:47:20 -0300 you wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> According to Documentation/driver-api/usb/URB.rst when a device
> is unplugged usb_submit_urb() returns -ENODEV.
>
> This error code propagates all the way up to usbnet_read_cmd() and
> usbnet_write_cmd() calls inside the smsc95xx.c driver during
> Ethernet cable unplug, unbind or reboot.
>
> [...]
Here is the summary with links:
- [v2,net] smsc95xx: Ignore -ENODEV errors when device is unplugged
https://git.kernel.org/netdev/net/c/c70c453abcbf
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:[~2022-03-07 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 20:47 [PATCH v2 net] smsc95xx: Ignore -ENODEV errors when device is unplugged Fabio Estevam
2022-03-07 12:40 ` patchwork-bot+netdevbpf [this message]
2022-03-09 13:32 ` (EXT) " Alexander Stein
2022-03-09 14:02 ` Alexander Stein
2022-03-09 16:41 ` Jakub Kicinski
2022-03-09 16:50 ` Fabio Estevam
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=164665681144.14619.4945223702291737274.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=fntoth@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marex@denx.de \
--cc=martyn.welch@collabora.com \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/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 NNTP newsgroup(s).