From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>,
john.mcnamara@intel.com, marko.kovacevic@intel.com
Cc: dev@dpdk.org, Hyong Youb Kim <hyonkim@cisco.com>
Subject: Re: [dpdk-dev] [PATCH] doc: update the enic guide and features
Date: Wed, 18 Jul 2018 11:22:08 +0100 [thread overview]
Message-ID: <3a6a65d9-9671-ad3f-99be-3777f7809934@intel.com> (raw)
In-Reply-To: <20180718021530.30079-1-johndale@cisco.com>
On 7/18/2018 3:15 AM, John Daley wrote:
> From: Hyong Youb Kim <hyonkim@cisco.com>
>
> Make a few updates in preparation for 18.08.
> - Use SPDX
> - Add 1400 series VIC adapters to supported models
> - Describe the VXLAN port number
> - Expand the description for ig-vlan-rewrite
> - Add inner RSS and checksum to the features
>
> Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
<...>
> @@ -534,4 +548,4 @@ Any questions or bugs should be reported to DPDK community and to the ENIC PMD
> maintainers:
>
> - John Daley <johndale@cisco.com>
> -- Nelson Escobar <neescoba@cisco.com>
> +- Hyong Youb Kim <hyonkim@cisco.com>
This information is duplication of MAINTAINERS file, what would you think
removing names from here and reference to maintainers file?
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-07-18 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 2:15 John Daley
2018-07-18 10:22 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-04 23:54 [dpdk-dev] [PATCH] net/enic: do not flush descriptor cache when opening vNIC John Daley
2018-04-04 23:54 ` [dpdk-dev] [PATCH] doc: update the enic guide and features John Daley
2018-04-06 16:42 ` 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=3a6a65d9-9671-ad3f-99be-3777f7809934@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.com \
--cc=marko.kovacevic@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).