From: Simon Horman <horms@kernel•org>
To: Jiawen Wu <jiawenwu@trustnetic•com>
Cc: netdev@vger•kernel.org, Andrew Lunn <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
"Russell King (Oracle)" <rmk+kernel@armlinux•org.uk>,
Mengyuan Lou <mengyuanlou@net-swift•com>
Subject: Re: [PATCH net-next 1/3] net: txgbe: expend SW-FW mailbox buffer size to identify QSFP module
Date: Mon, 29 Sep 2025 14:52:00 +0100 [thread overview]
Message-ID: <aNqPAH2q0sqxE6bX@horms.kernel.org> (raw)
In-Reply-To: <20250928093923.30456-2-jiawenwu@trustnetic.com>
On Sun, Sep 28, 2025 at 05:39:21PM +0800, Jiawen Wu wrote:
> In order to identify 40G and 100G QSFP modules, expend mailbox buffer
> size to store more information read from the firmware.
Hi,
I see that the message size is increased by 4 bytes,
including two new one-byte fields.
But I don't see how that is used by this patchset.
Could you expand on this a little?
>
> Signed-off-by: Jiawen Wu <jiawenwu@trustnetic•com>
...
next prev parent reply other threads:[~2025-09-29 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 9:39 [PATCH net-next 0/3] TXGBE feat new AML firmware Jiawen Wu
2025-09-28 9:39 ` [PATCH net-next 1/3] net: txgbe: expend SW-FW mailbox buffer size to identify QSFP module Jiawen Wu
2025-09-29 13:52 ` Simon Horman [this message]
2025-10-10 7:42 ` Jiawen Wu
2025-10-10 13:52 ` Andrew Lunn
2025-10-11 1:57 ` Jiawen Wu
2025-10-11 14:20 ` Andrew Lunn
2025-09-28 9:39 ` [PATCH net-next 2/3] net: txgbe: optimize the flow to setup PHY for AML devices Jiawen Wu
2025-09-30 1:39 ` Jakub Kicinski
2025-10-10 7:48 ` Jiawen Wu
2025-10-10 13:51 ` Andrew Lunn
2025-10-11 1:53 ` Jiawen Wu
2025-09-28 9:39 ` [PATCH net-next 3/3] net: txgbe: rename txgbe_get_phy_link() Jiawen Wu
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=aNqPAH2q0sqxE6bX@horms.kernel.org \
--to=horms@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jiawenwu@trustnetic$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mengyuanlou@net-swift$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rmk+kernel@armlinux$(echo .)org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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