From: "Gupta, Suraj" <suraj.gupta2@amd.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
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>,
Michal Simek <michal.simek@amd.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/6] net: xilinx: axienet: Add 10G/25G (XXV) ethernet support
Date: Tue, 1 Sep 2026 08:57:15 +0530 [thread overview]
Message-ID: <29d0926a-415d-4111-8378-7d7bc4087a04@amd.com> (raw)
In-Reply-To: <fe83c236-ce55-4c33-aa1f-23028e978696@lunn.ch>
On 9/1/2026 8:22 AM, Andrew Lunn wrote:
>> + /* This error handler runs only for the legacy embedded-DMA (1G) path,
>> + * whose mac_init() cannot fail, so its return value is not checked.
>> + */
>
> Is legacy the correct word here. Have you stopped licensing the 1G
> MAC?
>
> Andrew
By "legacy embedded-DMA (1G) path", I meant the legacy non-dmaengine
flow in the driver. This path does not use the dmaengine framework and
therefore does not communicate with the Xilinx DMAEngine driver;
instead, the AXI Ethernet driver handles the DMA programming directly.
I agree that "legacy embedded-DMA" could be confusing here. I'll rename
it to "non-dmaengine flow" in the next revision.
Thanks,
Suraj
next prev parent reply other threads:[~2026-09-01 3:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 15:08 [PATCH net-next v3 0/6] net: xilinx: axienet: Add 10G/25G (XXV) ethernet support Suraj Gupta
2026-08-31 15:08 ` [PATCH net-next v3 1/6] net: xilinx: axienet: Introduce axienet_config for MAC-specific ops Suraj Gupta
2026-09-01 15:09 ` sashiko-bot
2026-09-06 19:24 ` Gupta, Suraj
2026-08-31 15:08 ` [PATCH net-next v3 2/6] dt-bindings: net: xlnx,xxv-ethernet: Add Xilinx XXV 10G/25G Ethernet Suraj Gupta
2026-09-01 2:27 ` Andrew Lunn
2026-09-01 3:18 ` Gupta, Suraj
2026-09-01 14:31 ` Andrew Lunn
2026-09-01 17:01 ` Gupta, Suraj
2026-09-15 7:01 ` Gupta, Suraj
2026-08-31 15:08 ` [PATCH net-next v3 3/6] net: xilinx: axienet: Add 10G/25G (XXV) ethernet support Suraj Gupta
2026-09-01 2:52 ` Andrew Lunn
2026-09-01 3:27 ` Gupta, Suraj [this message]
2026-09-01 15:09 ` sashiko-bot
2026-09-06 19:41 ` Gupta, Suraj
2026-08-31 15:08 ` [PATCH net-next v3 4/6] net: xilinx: axienet: Make axienet_rmon_ranges non-static for reuse Suraj Gupta
2026-08-31 15:08 ` [PATCH net-next v3 5/6] net: xilinx: axienet: Dispatch statistics through axienet_config ops Suraj Gupta
2026-09-01 15:09 ` sashiko-bot
2026-09-06 19:25 ` Gupta, Suraj
2026-08-31 15:08 ` [PATCH net-next v3 6/6] net: xilinx: axienet: Add statistics support for XXV ethernet Suraj Gupta
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=29d0926a-415d-4111-8378-7d7bc4087a04@amd.com \
--to=suraj.gupta2@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.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 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.