From: patchwork-bot+netdevbpf@kernel.org
To: Miao@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Jun <jun.miao@intel.com>
Cc: o.rempel@pengutronix.de, kuba@kernel.org, oneukum@suse.com,
qiang.zhang@linux.dev, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: usb: enable the work after stop usbnet by ip down/up
Date: Thu, 10 Jul 2025 02:50:22 +0000 [thread overview]
Message-ID: <175211582275.967127.3179852673309162720.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708081653.307815-1-jun.miao@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Jul 2025 16:16:53 +0800 you wrote:
> From: Zqiang <qiang.zhang@linux.dev>
>
> Oleksij reported that:
> The smsc95xx driver fails after one down/up cycle, like this:
> $ nmcli device set enu1u1 managed no
> $ p a a 10.10.10.1/24 dev enu1u1
> $ ping -c 4 10.10.10.3
> $ ip l s dev enu1u1 down
> $ ip l s dev enu1u1 up
> $ ping -c 4 10.10.10.3
> The second ping does not reach the host. Networking also fails on other interfaces.
>
> [...]
Here is the summary with links:
- net: usb: enable the work after stop usbnet by ip down/up
https://git.kernel.org/netdev/net-next/c/6dfcbd7d1d65
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:[~2025-07-10 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 8:16 [PATCH] net: usb: enable the work after stop usbnet by ip down/up Jun Miao
2025-07-09 4:42 ` Oleksij Rempel
2025-07-09 5:31 ` Miao, Jun
2025-07-10 2:50 ` 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=175211582275.967127.3179852673309162720.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Miao@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=jun.miao@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=oneukum@suse.com \
--cc=qiang.zhang@linux.dev \
/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