From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>,
Ophir Munk <ophirmu@mellanox.com>,
dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] net/tap: fix report on multi segments capability
Date: Mon, 5 Feb 2018 18:02:37 +0000 [thread overview]
Message-ID: <7e3d9669-c8f9-9859-38af-34c74cd59323@intel.com> (raw)
In-Reply-To: <4a6a25e0-ee22-97f9-95bd-8feecd0ee9d2@6wind.com>
On 2/5/2018 2:53 PM, Pascal Mazon wrote:
>
> On 05/02/2018 11:59, Ophir Munk wrote:
>> TAP device is supporting multi segments Tx, however this capability is
>> not reported when querying the TAP device.
>> This commit adds this capability report.
>>
>> Fixes: 818fe14a9891 ("net/tap: use new Tx offloads API")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
> Acked-by: Pascal Mazon <pascal.mazon@6wind.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-02-05 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 10:59 Ophir Munk
2018-02-05 14:53 ` Pascal Mazon
2018-02-05 18:02 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-05 10:56 Ophir Munk
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=7e3d9669-c8f9-9859-38af-34c74cd59323@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=stable@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).