netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	richardcochran@gmail.com, linux@armlinux.org.uk,
	mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next 9/9] net: txgbe: Implement SRIOV for AML devices
Date: Tue, 20 May 2025 17:56:04 +0100	[thread overview]
Message-ID: <20250520165604.GF365796@horms.kernel.org> (raw)
In-Reply-To: <003c01dbc956$a2d65ed0$e8831c70$@trustnetic.com>

On Tue, May 20, 2025 at 03:13:07PM +0800, Jiawen Wu wrote:
> On Mon, May 19, 2025 11:59 PM, Simon Horman wrote:
> > On Fri, May 16, 2025 at 05:32:20PM +0800, Jiawen Wu wrote:
> > > Support to bring VFs link up for AML 25G/10G devices.
> > 
> > Hi Jiawen,
> > 
> > I think this warrants a bit more explanation: what is required for
> > these devices; and perhaps how that differs from other devices.
> 
> For the chip design, the PHY/PCS attached AML 25G/10G devices is
> different from SP devices (wx_mac_sp). And the read/write of I2C and
> PHY/PCS are controlled by firmware, which is described in patch(4/9).
> So the different PHYLINK mode is added for AML devices.
> And for this patch, the SRIOV related function is added since the functions
> .mac_link_up and .mac_link_down are changed.

Thanks.

Just to clarify my previous email: I meant that it would be nice
to include a bit more information in the commit message.

...

      reply	other threads:[~2025-05-20 16:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250516093220.6044-1-jiawenwu@trustnetic.com>
2025-05-16  9:32 ` [PATCH net-next 1/9] net: txgbe: Remove specified SP type Jiawen Wu
2025-05-20 16:56   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 2/9] net: wangxun: Use specific flag bit to simplify the code Jiawen Wu
2025-05-20 16:56   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 3/9] net: txgbe: Distinguish between 40G and 25G devices Jiawen Wu
2025-05-20 16:56   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 4/9] net: txgbe: Implement PHYLINK for AML 25G/10G devices Jiawen Wu
2025-05-20 16:57   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 5/9] net: txgbe: Support to handle GPIO IRQs for AML devices Jiawen Wu
2025-05-20 16:57   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 6/9] net: txgbe: Correct the currect link settings Jiawen Wu
2025-05-20 16:57   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 7/9] net: txgbe: Restrict the use of mismatched FW versions Jiawen Wu
2025-05-20 16:58   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 8/9] net: txgbe: Implement PTP for AML devices Jiawen Wu
2025-05-20 16:58   ` Simon Horman
2025-05-16  9:32 ` [PATCH net-next 9/9] net: txgbe: Implement SRIOV " Jiawen Wu
2025-05-19 15:58   ` Simon Horman
2025-05-20  7:13     ` Jiawen Wu
2025-05-20 16:56       ` Simon Horman [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=20250520165604.GF365796@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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).