All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dai, Wei" <wei.dai@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v4] net/ixgbe: add support of 2.5G and 5G on X550
Date: Wed, 26 Jul 2017 23:57:33 +0000	[thread overview]
Message-ID: <49759EB36A64CF4892C1AFEC9231E8D650B68F33@PGSMSX106.gar.corp.intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B67CE31@shsmsx102.ccr.corp.intel.com>



> -----Original Message-----
> From: Lu, Wenzhuo
> Sent: Thursday, July 27, 2017 12:59 AM
> To: Dai, Wei <wei.dai@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH v4] net/ixgbe: add support of 2.5G and 5G on X550
> 
> Hi Wei,
> 
> > -----Original Message-----
> > From: Dai, Wei
> > Sent: Wednesday, July 26, 2017 11:30 AM
> > To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Ananyev, Konstantin
> > <konstantin.ananyev@intel.com>
> > Cc: dev@dpdk.org; Dai, Wei <wei.dai@intel.com>
> > Subject: [PATCH v4] net/ixgbe: add support of 2.5G and 5G on X550
> >
> > This patch adds support of 2.5G and 5G ethernet interface on X550.
> >
> > Signed-off-by: Wei Dai <wei.dai@intel.com>
> > ---
> >  drivers/net/ixgbe/base/ixgbe_type.h |  5 +++++
> >  drivers/net/ixgbe/ixgbe_ethdev.c    | 27
> ++++++++++++++++++++++++---
> >  2 files changed, 29 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/ixgbe/base/ixgbe_type.h
> > b/drivers/net/ixgbe/base/ixgbe_type.h
> > index bda8558..3fd5425 100644
> > --- a/drivers/net/ixgbe/base/ixgbe_type.h
> > +++ b/drivers/net/ixgbe/base/ixgbe_type.h
> > @@ -3408,6 +3408,11 @@ typedef u32 ixgbe_link_speed;  #define
> > IXGBE_LINK_SPEED_82599_AUTONEG
> > 	(IXGBE_LINK_SPEED_100_FULL | \
> >  					 IXGBE_LINK_SPEED_1GB_FULL | \
> >  					 IXGBE_LINK_SPEED_10GB_FULL)
> > +#define IXGBE_LINK_SPEED_X550_AUTONEG
> > 	(IXGBE_LINK_SPEED_100_FULL | \
> > +					IXGBE_LINK_SPEED_1GB_FULL | \
> > +					IXGBE_LINK_SPEED_2_5GB_FULL | \
> > +					IXGBE_LINK_SPEED_5GB_FULL | \
> > +					IXGBE_LINK_SPEED_10GB_FULL)
> Just noticed you changed base code. As we discussed before, I don't mean
> that. Actually, I suggest to put it in, for example, ixgbe_ethdev.h
Yes, you are right. Your method is better.
I will follow it in my v5 patch.

  reply	other threads:[~2017-07-26 23:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  2:00 [PATCH] net/ixgbe: add support of 2.5G and 5G Wei Dai
2017-07-26  9:29 ` [PATCH v2] net/ixgbe: add support of 2.5G and 5G on X550 Wei Dai
2017-07-26 13:26   ` Lu, Wenzhuo
2017-07-26 14:10     ` Dai, Wei
2017-07-26 14:13       ` Lu, Wenzhuo
2017-07-26 14:31         ` Dai, Wei
2017-07-26 14:43   ` [PATCH v3] " Wei Dai
2017-07-26 15:01     ` Lu, Wenzhuo
2017-07-26 15:27       ` Dai, Wei
2017-07-26 15:29     ` [PATCH v4] " Wei Dai
2017-07-26 16:59       ` Lu, Wenzhuo
2017-07-26 23:57         ` Dai, Wei [this message]
2017-07-27  1:02       ` [PATCH v5] " Wei Dai
2017-07-27  1:07         ` Lu, Wenzhuo
2017-07-31 13:14         ` Ferruh Yigit
2017-07-31 17:48           ` Lu, Wenzhuo
2017-07-31 18:12 ` [PATCH v6] " Wenzhuo Lu
2017-07-31 18:19   ` 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=49759EB36A64CF4892C1AFEC9231E8D650B68F33@PGSMSX106.gar.corp.intel.com \
    --to=wei.dai@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=wenzhuo.lu@intel.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 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.