From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] net/tap: remove useless offload setup
Date: Fri, 2 Jul 2021 16:36:53 +0300 [thread overview]
Message-ID: <a1e62e6a-9148-260e-856f-efc2ef22b4c8@oktetlabs.ru> (raw)
In-Reply-To: <0535E18A-5F47-4C58-8632-DAA5EA85FBCF@intel.com>
On 7/2/21 4:26 PM, Wiles, Keith wrote:
>
>
>> On Jun 15, 2021, at 11:15 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>>
>> This looks like some infrastructure that was set for some future
>> change that never happened. Remove it.
>>
>> Stephen Hemminger (2):
>> tap: remove useless offload capa functions
>> tap: replace offload_capa function with define
>>
>> drivers/net/tap/rte_eth_tap.c | 58 +++++++++--------------------------
>> 1 file changed, 15 insertions(+), 43 deletions(-)
>>
>> --
>> 2.30.2
>>
>
> Acked-by: Keith Wiles<Keith.wiles@intel.com> for the series.
Applied, thanks.
prev parent reply other threads:[~2021-07-02 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 4:15 Stephen Hemminger
2021-06-16 4:15 ` [dpdk-dev] [PATCH 1/2] net/tap: remove useless offload capa functions Stephen Hemminger
2021-07-01 14:16 ` Andrew Rybchenko
2021-07-01 17:18 ` Stephen Hemminger
2021-07-01 19:19 ` Wiles, Keith
2021-07-02 7:56 ` Andrew Rybchenko
2021-06-16 4:15 ` [dpdk-dev] [PATCH 2/2] net/tap: replace offload_capa function with define Stephen Hemminger
2021-07-01 14:18 ` Andrew Rybchenko
2021-07-02 13:26 ` [dpdk-dev] [PATCH 0/2] net/tap: remove useless offload setup Wiles, Keith
2021-07-02 13:36 ` Andrew Rybchenko [this message]
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=a1e62e6a-9148-260e-856f-efc2ef22b4c8@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=stephen@networkplumber.org \
/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).