From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: remove device-specific comments from VLAN API
Date: Wed, 5 Aug 2020 17:57:47 +0100 [thread overview]
Message-ID: <8ce1de6b-3812-26af-9bfe-bd62067ad6a3@intel.com> (raw)
In-Reply-To: <5bd9f5e8-8b72-fb57-982f-1f487702a723@solarflare.com>
On 8/5/2020 12:27 PM, Andrew Rybchenko wrote:
> On 8/4/20 12:48 PM, Thomas Monjalon wrote:
>> Some confusing comments were still present from old days,
>> when most drivers were from Intel.
>>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2020-08-05 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 9:41 [dpdk-dev] [PATCH] " Thomas Monjalon
2020-08-04 9:48 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-08-05 9:19 ` David Marchand
2020-08-05 11:27 ` Andrew Rybchenko
2020-08-05 16:57 ` Ferruh Yigit [this message]
2020-08-05 18:02 ` 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=8ce1de6b-3812-26af-9bfe-bd62067ad6a3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--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 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).