From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jeff Guo <jia.guo@intel.com>,
qi.z.zhang@intel.com, beilei.xing@intel.com,
jingjing.wu@intel.com
Cc: dev@dpdk.org, junfeng.guo@intel.com, simei.su@intel.com
Subject: Re: [dpdk-dev] [dpdk-dev v1] net/iavf: delete unsupported rss types
Date: Fri, 24 Jul 2020 10:36:46 +0100 [thread overview]
Message-ID: <88b44f9d-bca4-263e-58d2-6f0bd664145d@intel.com> (raw)
In-Reply-To: <20200724040702.9887-1-jia.guo@intel.com>
On 7/24/2020 5:07 AM, Jeff Guo wrote:
> The combined hash type should be bound with prefix protocol when
> configure it, so delete some useless and unsupported part for
> rss types mapping.
>
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
Hi Jeff,
Can you please add the fixes line as reference? There is a refactoring in the
middle, so I assume patch wouldn't be candidate for backport, but still good to
document the fixed commit.
<...>
next prev parent reply other threads:[~2020-07-24 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 4:07 Jeff Guo
2020-07-24 9:00 ` Zhang, Qi Z
2020-07-24 9:36 ` Ferruh Yigit [this message]
2020-07-24 9:51 ` Guo, Jia
2020-07-24 9:55 ` Zhang, Qi Z
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=88b44f9d-bca4-263e-58d2-6f0bd664145d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=simei.su@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).