From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Namburu, Chandu-babu" <chandu@amd.com>,
"Sebastian, Selwin" <Selwin.Sebastian@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v1 1/2] net/axgbe: add support for Yellow Carp ethernet device
Date: Thu, 3 Feb 2022 11:56:43 +0000 [thread overview]
Message-ID: <4962b004-b24a-ca47-2cea-34a59b303b28@intel.com> (raw)
In-Reply-To: <MW2PR12MB25386F08A0DF54B577BB9084C8259@MW2PR12MB2538.namprd12.prod.outlook.com>
On 1/31/2022 6:48 AM, Namburu, Chandu-babu wrote:
> [Public]
>
>
>
> -----Original Message-----
> From: Sebastian, Selwin <Selwin.Sebastian@amd.com>
> Sent: Monday, January 31, 2022 11:09 AM
> To: dev@dpdk.org
> Cc: Namburu, Chandu-babu <chandu@amd.com>; ferruh.yigit@intel.com
> Subject: [PATCH v1 1/2] net/axgbe: add support for Yellow Carp ethernet device
>
> From: Selwin Sebastian <selwin.sebastian@amd.com>
>
> Yellow Carp ethernet devices (V3xxx) use the existing PCI ID but the window settings for the indirect PCS access have been altered. Add the check for Yellow Carp Ethernet devices to use the new register values.
>
> Signed-off-by: Selwin Sebastian <selwin.sebastian@amd.com>
<...>
>
> For series,
> Acked-by: Chandubabu Namburu <chandu@amd.com>
Series applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2022-02-03 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 5:39 [PATCH v1 0/2] net/axgbe: Add support for Yellow Carp ethernet ssebasti
2022-01-31 5:39 ` [PATCH v1 1/2] net/axgbe: add support for Yellow Carp ethernet device ssebasti
2022-01-31 6:48 ` Namburu, Chandu-babu
2022-02-03 11:56 ` Ferruh Yigit [this message]
2022-02-01 14:26 ` Ferruh Yigit
2022-02-02 8:56 ` Sebastian, Selwin
2022-02-02 10:53 ` Ferruh Yigit
2022-02-02 11:56 ` Sebastian, Selwin
2022-01-31 5:39 ` [PATCH v1 2/2] net/axgbe: disable the CDR wa for Yellow Carp devices ssebasti
2022-02-01 14:23 ` [PATCH v1 0/2] net/axgbe: Add support for Yellow Carp ethernet Ferruh Yigit
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=4962b004-b24a-ca47-2cea-34a59b303b28@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Selwin.Sebastian@amd.com \
--cc=chandu@amd.com \
--cc=dev@dpdk.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 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).