From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Sun, Chenmin" <chenmin.sun@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ice: fixed speed capability error issue
Date: Fri, 29 Mar 2019 08:25:30 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611533567BC@SHSMSX103.ccr.corp.intel.com> (raw)
Message-ID: <20190329082530.fBvj-bBmqAUTYckUwjPlvwTh0FUw7G7AmXm7NxxuKXQ@z> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC0909407F1B45@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lu, Wenzhuo
> Sent: Friday, March 29, 2019 11:22 AM
> To: Sun, Chenmin <chenmin.sun@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] net/ice: fixed speed capability error issue
>
> Hi,
>
>
> > -----Original Message-----
> > From: Sun, Chenmin
> > Sent: Friday, March 29, 2019 5:54 PM
> > To: dev@dpdk.org
> > Cc: Sun, Chenmin <chenmin.sun@intel.com>; Lu, Wenzhuo
> > <wenzhuo.lu@intel.com>
> > Subject: [PATCH] net/ice: fixed speed capability error issue
> >
> > From: Chenmin Sun <chenmin.sun@intel.com>
> >
> > Device speed capability should be specified based on different phy
> > types instead of a fixed value, this patch fix the issue.
> >
> > Fixes: 690175ee51bf ("net/ice: support getting device information")
> > Cc: wenzhuo.lu@intel.com
> >
> > Signed-off-by: Chenmin Sun <chenmin.sun@intel.com>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2019-03-29 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 9:53 chenmin.sun
2019-03-29 3:21 ` Lu, Wenzhuo
2019-03-29 3:21 ` Lu, Wenzhuo
2019-03-29 8:25 ` Zhang, Qi Z [this message]
2019-03-29 8:25 ` Zhang, Qi Z
2019-03-29 9:53 ` chenmin.sun
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=039ED4275CED7440929022BC67E70611533567BC@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=chenmin.sun@intel.com \
--cc=dev@dpdk.org \
--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 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).