DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <ssebasti@amd.com>, <dev@dpdk.org>
Cc: <chandu@amd.com>
Subject: Re: [PATCH v1 0/2] net/axgbe: Add support for Yellow Carp ethernet
Date: Tue, 1 Feb 2022 14:23:36 +0000	[thread overview]
Message-ID: <204f64f0-f308-b9a8-9a77-0b7c55316783@intel.com> (raw)
In-Reply-To: <20220131053920.167230-1-ssebasti@amd.com>

On 1/31/2022 5:39 AM, ssebasti@amd.com wrote:
> From: Selwin Sebastian <selwin.sebastian@amd.com>
> 
> Adding support for Yellow Carp ethernet device
> 

Hi Selwin,

Since you are referring to this new device (Yellow Carp), can you please
point to some documentation for it, better in the documentation but at
least in the commit log.

And if this device support is important enough, you can add this into the
release notes.

> Selwin Sebastian (2):
>    net/axgbe: add support for Yellow Carp ethernet device
>    net/axgbe: disable the CDR wa for Yellow Carp devices
> 
>   drivers/net/axgbe/axgbe_common.h |  2 ++
>   drivers/net/axgbe/axgbe_ethdev.c | 36 ++++++++++++++++++++++----------
>   2 files changed, 27 insertions(+), 11 deletions(-)
> 


      parent reply	other threads:[~2022-02-01 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  5:39 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
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 ` Ferruh Yigit [this message]

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=204f64f0-f308-b9a8-9a77-0b7c55316783@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=chandu@amd.com \
    --cc=dev@dpdk.org \
    --cc=ssebasti@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).