From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, <viveksharma@marvell.com>,
<dev@dpdk.org>
Cc: <intoviveksharma@gmail.com>, <thomas@monjalon.net>,
<stephen@networkplumber.org>, <ramirose@gmail.com>,
<jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v4] ethdev: support QinQ strip dynamic configuration
Date: Wed, 3 Jul 2019 22:55:55 +0300 [thread overview]
Message-ID: <46667eb0-e50e-f9ca-d80a-49b900b1853d@solarflare.com> (raw)
In-Reply-To: <c5de055c-5ec7-4659-9b50-cbac997afc40@intel.com>
On 03.07.2019 20:48, Ferruh Yigit wrote:
> On 7/2/2019 4:37 AM, viveksharma@marvell.com wrote:
>> From: Vivek Sharma <viveksharma@marvell.com>
>>
>> Enable missing support for runtime configuration (setting/getting)
>> of QinQ strip rx offload for a given ethdev.
>>
>> Signed-off-by: Vivek Sharma <viveksharma@marvell.com>
> Hi Andrew,
>
> As far as I understand you were OK with the patch after change, can I add your ack?
Yes, please. I've tried to find some time to double-check consistency
vs supported offloads and error reporting, but have not found time yet
to do it. Let's apply and I'll keep it in mind to take a look later.
Thanks,
Andrew.
next prev parent reply other threads:[~2019-07-03 19:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 11:11 [dpdk-dev] [PATCH] ethdev: fix QinQ strip offload support viveksharma
2019-04-14 11:11 ` viveksharma
2019-04-15 15:54 ` Stephen Hemminger
2019-04-15 15:54 ` Stephen Hemminger
2019-04-15 21:33 ` Rami Rosen
2019-04-15 21:33 ` Rami Rosen
2019-04-17 7:40 ` [dpdk-dev] [PATCH v2] " viveksharma
2019-04-17 7:40 ` viveksharma
2019-04-17 8:34 ` Thomas Monjalon
2019-04-17 8:34 ` Thomas Monjalon
2019-04-18 7:38 ` [dpdk-dev] [EXT] " Vivek Kumar Sharma
2019-04-18 7:38 ` Vivek Kumar Sharma
2019-04-18 8:07 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-04-18 8:07 ` Thomas Monjalon
2019-04-19 5:59 ` [dpdk-dev] [PATCH v3] ethdev: support QinQ strip dynamic configuration viveksharma
2019-04-19 5:59 ` viveksharma
2019-06-27 11:08 ` Ferruh Yigit
2019-07-01 10:07 ` Andrew Rybchenko
2019-07-01 13:05 ` Ferruh Yigit
2019-07-02 3:37 ` [dpdk-dev] [PATCH v4] " viveksharma
2019-07-03 17:48 ` Ferruh Yigit
2019-07-03 19:55 ` Andrew Rybchenko [this message]
2019-07-04 9:41 ` Ferruh Yigit
2019-07-04 10:05 ` 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=46667eb0-e50e-f9ca-d80a-49b900b1853d@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=intoviveksharma@gmail.com \
--cc=jerinj@marvell.com \
--cc=ramirose@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viveksharma@marvell.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).