All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: None <yicongsrfy@163.com>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, andrew@lunn.ch,
	oneukum@suse.com, davem@davemloft.net, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, yicong@kylinos.cn
Subject: Re: [PATCH v2] usbnet: Set duplex status to unknown in the absence of MII
Date: Fri, 25 Jul 2025 18:10:20 +0000	[thread overview]
Message-ID: <175346702056.3223523.12381590141591970711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724013133.1645142-1-yicongsrfy@163.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 24 Jul 2025 09:31:33 +0800 you wrote:
> From: Yi Cong <yicong@kylinos.cn>
> 
> Currently, USB CDC devices that do not use MDIO to get link status have
> their duplex mode set to half-duplex by default. However, since the CDC
> specification does not define a duplex status, this can be misleading.
> 
> This patch changes the default to DUPLEX_UNKNOWN in the absence of MII,
> which more accurately reflects the state of the link and avoids implying
> an incorrect or error state.
> 
> [...]

Here is the summary with links:
  - [v2] usbnet: Set duplex status to unknown in the absence of MII
    https://git.kernel.org/netdev/net-next/c/a75afcd188e1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-07-25 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21  7:10 [PATCH] usbnet: Set duplex status to unknown in the absence of MII yicongsrfy
2025-07-21 13:51 ` Andrew Lunn
2025-07-22  2:09   ` yicongsrfy
2025-07-22 13:06     ` Andrew Lunn
2025-07-23  1:29       ` yicongsrfy
2025-07-23  7:17         ` Oliver Neukum
2025-07-23  8:44           ` yicongsrfy
2025-07-23 10:03             ` Oliver Neukum
2025-07-23 13:04             ` Andrew Lunn
2025-07-23 13:05         ` Andrew Lunn
2025-07-23 22:21           ` Jakub Kicinski
2025-07-24  1:31             ` [PATCH v2] " yicongsrfy
2025-07-24  9:03               ` Oliver Neukum
2025-07-25 18: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=175346702056.3223523.12381590141591970711.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=yicong@kylinos.cn \
    --cc=yicongsrfy@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.