From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>, David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] devtools: add more headline case rules
Date: Thu, 5 Mar 2020 18:42:54 +0300 [thread overview]
Message-ID: <d468a99e-7993-e24c-550f-d707eada5bee@solarflare.com> (raw)
In-Reply-To: <ecb15f6a-05b1-ce64-c6e7-d82c4fa71cce@intel.com>
On 3/5/20 6:39 PM, Ferruh Yigit wrote:
> On 3/5/2020 3:08 PM, Andrew Rybchenko wrote:
>> On 3/5/20 5:55 PM, Ferruh Yigit wrote:
>>> BAR -> Base Address Register
>>> FDIR -> Flow Director
>>> GENEVE -> Generic Network Virtualization Encapsulation
>>> IO -> Input/Output
>>> MPLS -> Multiprotocol Label Switching
>>> NEON
>>> null
>>> NVGRE -> Network Virtualization using Generic Routing Encapsulation
>>> OOB -> Out Of Bounds
>>> RDMA -> Remote Direct Memory Access
>>> TC -> Traffic Class
>>> VFIO -> Virtual Function I/O
>>> VXLAN -> Virtual Extensible LAN
>>> XDP -> eXpress Data Path
>>>
>>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>>
>> I'm not sure about 'null'. Otherwise
>
> I have no preference on it, but that is from the git history, so just to be
> consistent.
OK, makes sense.
>>
>> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
>>
>
next prev parent reply other threads:[~2020-03-05 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 14:55 [dpdk-dev] [PATCH] devtools: add more headline case rules Ferruh Yigit
2020-03-05 15:08 ` Andrew Rybchenko
2020-03-05 15:39 ` Ferruh Yigit
2020-03-05 15:42 ` Andrew Rybchenko [this message]
2020-03-05 15:11 ` Thomas Monjalon
2020-03-05 16:06 ` Ferruh Yigit
2020-03-05 16:35 ` Thomas Monjalon
2020-03-05 17:43 ` Ferruh Yigit
2020-03-06 14:32 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2020-03-06 18:44 ` Thomas Monjalon
2020-05-20 10:25 [dpdk-dev] [PATCH] " Ferruh Yigit
2020-05-24 21:01 ` Thomas Monjalon
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=d468a99e-7993-e24c-550f-d707eada5bee@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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.