From: patchwork-bot+netdevbpf@kernel.org
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, yongqin.liu@linaro.org,
a.miederhoefer@gmx.de, arne_f@ipfire.org
Subject: Re: [PATCH] net: usb: ax88179_178a: improve reset check
Date: Wed, 19 Jun 2024 09:50:29 +0000 [thread overview]
Message-ID: <171879062901.26288.8596567430830957012.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240617102839.654316-1-jtornosm@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 17 Jun 2024 12:28:21 +0200 you wrote:
> After ecf848eb934b ("net: usb: ax88179_178a: fix link status when link is
> set to down/up") to not reset from usbnet_open after the reset from
> usbnet_probe at initialization stage to speed up this, some issues have
> been reported.
>
> It seems to happen that if the initialization is slower, and some time
> passes between the probe operation and the open operation, the second reset
> from open is necessary too to have the device working. The reason is that
> if there is no activity with the phy, this is "disconnected".
>
> [...]
Here is the summary with links:
- net: usb: ax88179_178a: improve reset check
https://git.kernel.org/netdev/net/c/7be4cb7189f7
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:[~2024-06-19 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 10:28 [PATCH] net: usb: ax88179_178a: improve reset check Jose Ignacio Tornos Martinez
2024-06-19 9:50 ` patchwork-bot+netdevbpf [this message]
2024-06-19 10:37 ` Arne Fitzenreiter
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=171879062901.26288.8596567430830957012.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.miederhoefer@gmx.de \
--cc=arne_f@ipfire.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yongqin.liu@linaro.org \
/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