From: Stephen Hemminger <stephen@networkplumber.org>
To: Vinay Govindaiah <vigovind@amd.com>
Cc: <dev@dpdk.org>, <selwin.sebastian@amd.com>
Subject: Re: [PATCH] net/axgbe: add support for V4000 Kracken2e
Date: Tue, 2 Dec 2025 15:56:53 -0800 [thread overview]
Message-ID: <20251202155653.05f83806@phoenix.local> (raw)
In-Reply-To: <20251202071152.317942-1-vigovind@amd.com>
On Tue, 2 Dec 2025 12:41:52 +0530
Vinay Govindaiah <vigovind@amd.com> wrote:
> add device ID's for Kracken2e to enable
> driver to support this device.
>
> Signed-off-by: Vinay Govindaiah <vigovind@amd.com>
> ---
Applied to next-net after fixing the incorrect indentation
in the switch statement.
next prev parent reply other threads:[~2025-12-02 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 7:11 Vinay Govindaiah
2025-12-02 7:37 ` Sebastian, Selwin
2025-12-02 23:56 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-02 6:43 [PATCH] net/axgbe:Add " Vinay Govindaiah
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=20251202155653.05f83806@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=selwin.sebastian@amd.com \
--cc=vigovind@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).