From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, glance@acc.umu.se, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lukas@wunner.de
Subject: Re: [PATCH net v1 1/2] net: asix: fix "can't send until first packet is send" issue
Date: Tue, 28 Jun 2022 05:10:13 +0000 [thread overview]
Message-ID: <165639301319.30025.6669854790252095765.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220624075139.3139300-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 24 Jun 2022 09:51:38 +0200 you wrote:
> If cable is attached after probe sequence, the usbnet framework would
> not automatically start processing RX packets except at least one
> packet was transmitted.
>
> On systems with any kind of address auto configuration this issue was
> not detected, because some packets are send immediately after link state
> is changed to "running".
>
> [...]
Here is the summary with links:
- [net,v1,1/2] net: asix: fix "can't send until first packet is send" issue
https://git.kernel.org/netdev/net/c/805206e66fab
- [net,v1,2/2] net: usb: asix: do not force pause frames support
https://git.kernel.org/netdev/net/c/ce95ab775f8d
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:[~2022-06-28 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 7:51 [PATCH net v1 1/2] net: asix: fix "can't send until first packet is send" issue Oleksij Rempel
2022-06-24 7:51 ` [PATCH net v1 2/2] net: usb: asix: do not force pause frames support Oleksij Rempel
2022-06-28 4:49 ` Oleksij Rempel
2022-06-28 4:49 ` [PATCH net v1 1/2] net: asix: fix "can't send until first packet is send" issue Oleksij Rempel
2022-06-28 7:50 ` Lucas Stach
2022-06-28 8:00 ` Oleksij Rempel
2022-06-28 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=165639301319.30025.6669854790252095765.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=glance@acc.umu.se \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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