From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Suraj Gupta <suraj.gupta2@amd.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, git@amd.com,
harini.katakam@amd.com
Subject: Re: [PATCH net-next V2 2/2] net: axienet: Add support for 2500base-X only configuration.
Date: Wed, 12 Mar 2025 12:06:21 +0100 [thread overview]
Message-ID: <93f1c6d0-a1fe-4154-a31d-20cc878476d9@linux.intel.com> (raw)
In-Reply-To: <20250312095411.1392379-3-suraj.gupta2@amd.com>
On 2025-03-12 10:54 AM, Suraj Gupta wrote:
> AXI 1G/2.5G ethernet IP has following synthesis options:
> 1) SGMII/1000base-X only.
> 2) 2500base-X only.
> 3) dynamically switching between (1) and (2).
> Add support for 2500base-X only configuration.
Hi, thanks for the patch.
nit: a discrepancy between the commit description for and the comments
in the code for 3)
Maybe adding that information here in the commit description would make
sense as well? Or giving a bit of a background that SGMII/1000base-X is
already implemented in the driver and you are adding 2500base-X only
support.
> + /* AXI 1G/2.5G ethernet IP has following synthesis options:
> + * 1) SGMII/1000base-X only.
> + * 2) 2500base-X only.
> + * 3) Dynamically switching between (1) and (2), and is not
> + * implemented in driver.
> + */
For the rest of the patch, it looks good to me but I'd rather have
someone more experienced provide the Reviewed-By tag if they find the
patch appropriate.
Best regards,
Dawid
next prev parent reply other threads:[~2025-03-12 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:54 [PATCH net-next V2 0/2] Add support for 2500Base-X only configuration Suraj Gupta
2025-03-12 9:54 ` [PATCH net-next V2 1/2] dt-bindings: net: xlnx,axi-ethernet: Modify descriptions and phy-mode value to support 2500base-X " Suraj Gupta
2025-03-12 13:17 ` Rob Herring
2025-03-12 9:54 ` [PATCH net-next V2 2/2] net: axienet: Add support for " Suraj Gupta
2025-03-12 11:06 ` Dawid Osuchowski [this message]
2025-03-12 13:25 ` Andrew Lunn
2025-03-12 14:13 ` Russell King (Oracle)
2025-03-12 14:49 ` Gupta, Suraj
2025-03-12 14:58 ` Andrew Lunn
2025-03-12 15:06 ` Gupta, Suraj
2025-03-12 15:33 ` Andrew Lunn
2025-03-12 16:08 ` Gupta, Suraj
2025-03-12 19:02 ` Andrew Lunn
2025-03-12 19:40 ` Russell King (Oracle)
2025-03-12 22:10 ` Andrew Lunn
2025-03-13 3:31 ` Gupta, Suraj
2025-03-13 7:34 ` Gupta, Suraj
2025-03-13 12:47 ` Andrew Lunn
2025-03-19 18:41 ` Gupta, Suraj
2025-03-13 12:54 ` Andrew Lunn
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=93f1c6d0-a1fe-4154-a31d-20cc878476d9@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=suraj.gupta2@amd.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).