From: patchwork-bot+netdevbpf@kernel.org
To: Foster Snowhill <forst@pen.gy>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, gvalkov@gmail.com, oneukum@suse.com,
netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next 1/5] usbnet: ipheth: race between ipheth_close and error handling
Date: Fri, 09 Aug 2024 13:00:40 +0000 [thread overview]
Message-ID: <172320844026.3782387.2037318141249570355.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240806172809.675044-1-forst@pen.gy>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 6 Aug 2024 19:28:05 +0200 you wrote:
> From: Oliver Neukum <oneukum@suse.com>
>
> ipheth_sndbulk_callback() can submit carrier_work
> as a part of its error handling. That means that
> the driver must make sure that the work is cancelled
> after it has made sure that no more URB can terminate
> with an error condition.
>
> [...]
Here is the summary with links:
- [net-next,1/5] usbnet: ipheth: race between ipheth_close and error handling
https://git.kernel.org/netdev/net/c/e5876b088ba0
- [net-next,2/5] usbnet: ipheth: remove extraneous rx URB length check
https://git.kernel.org/netdev/net/c/655b46d7a39a
- [net-next,3/5] usbnet: ipheth: drop RX URBs with no payload
https://git.kernel.org/netdev/net/c/94d7eeb6c0ef
- [net-next,4/5] usbnet: ipheth: do not stop RX on failing RX callback
https://git.kernel.org/netdev/net/c/74efed51e0a4
- [net-next,5/5] usbnet: ipheth: fix carrier detection in modes 1 and 4
https://git.kernel.org/netdev/net/c/67927a1b255d
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:[~2024-08-09 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 17:28 [PATCH net-next 1/5] usbnet: ipheth: race between ipheth_close and error handling Foster Snowhill
2024-08-06 17:28 ` [PATCH net-next 2/5] usbnet: ipheth: remove extraneous rx URB length check Foster Snowhill
2024-08-09 10:16 ` Simon Horman
2024-09-07 23:21 ` Foster Snowhill
2024-08-06 17:28 ` [PATCH net-next 3/5] usbnet: ipheth: drop RX URBs with no payload Foster Snowhill
2024-08-06 17:28 ` [PATCH net-next 4/5] usbnet: ipheth: do not stop RX on failing RX callback Foster Snowhill
2024-08-06 17:28 ` [PATCH net-next 5/5] usbnet: ipheth: fix carrier detection in modes 1 and 4 Foster Snowhill
2024-08-09 13:00 ` 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=172320844026.3782387.2037318141249570355.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=forst@pen.gy \
--cc=gvalkov@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).