From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] net/sfc: improve Rx checksumming support
Date: Thu, 19 Jul 2018 19:28:36 +0300 [thread overview]
Message-ID: <008b8fc8-3ef4-b48a-5b90-9aff746ac452@solarflare.com> (raw)
In-Reply-To: <0d53ad00-d432-f6c8-6d14-46f21053e150@solarflare.com>
On 19.07.2018 19:07, Andrew Rybchenko wrote:
> On 19.07.2018 13:56, Ferruh Yigit wrote:
>> On 7/15/2018 10:56 AM, Andrew Rybchenko wrote:
>>> Andrew Rybchenko (3):
>>> net/sfc: move Rx checksum offload check to device level
>>> net/sfc: fix Rx queue offloads reporting in queue info
>>> net/sfc: prepare to support Rx datapath without checksum
>> Hi Andrew,
>>
>> These conflict with another sfc patchset already applied, would you mind
>> rebasing the set on top of latest next-net?
>
> Hi Ferruh,
>
> yes, of course.
It looks like it is already applied and pushed to next-net:
http://git.dpdk.org/next/dpdk-next-net/commit/?id=bd3c7e3f7eb54325aeffefe91c269a58dc63de9a
http://git.dpdk.org/next/dpdk-next-net/commit/?id=607b9ecf2354aeeacb52121c4f3b4f9ad1cc907c
http://git.dpdk.org/next/dpdk-next-net/commit/?id=b0cd127737030859fca09c68a366f6a1c43ba6d1
If so, I'm not sure that I understand the request.
Andrew.
next prev parent reply other threads:[~2018-07-19 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 9:56 Andrew Rybchenko
2018-07-15 9:56 ` [dpdk-dev] [PATCH 1/3] net/sfc: move Rx checksum offload check to device level Andrew Rybchenko
2018-07-15 9:56 ` [dpdk-dev] [PATCH 2/3] net/sfc: fix Rx queue offloads reporting in queue info Andrew Rybchenko
2018-07-15 9:56 ` [dpdk-dev] [PATCH 3/3] net/sfc: prepare to support Rx datapath without checksum Andrew Rybchenko
2018-07-19 10:56 ` [dpdk-dev] [PATCH 0/3] net/sfc: improve Rx checksumming support Ferruh Yigit
2018-07-19 16:07 ` Andrew Rybchenko
2018-07-19 16:28 ` Andrew Rybchenko [this message]
2018-07-20 8:55 ` Ferruh Yigit
2018-07-20 8:56 ` 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=008b8fc8-3ef4-b48a-5b90-9aff746ac452@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).