From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/nfp: remove reference to old offload API
Date: Wed, 23 May 2018 16:52:16 +0100 [thread overview]
Message-ID: <b29a8f34-98ab-f1e6-fcbf-08cdb6a2ddf4@intel.com> (raw)
In-Reply-To: <1527070484-35412-1-git-send-email-alejandro.lucero@netronome.com>
On 5/23/2018 11:14 AM, Alejandro Lucero wrote:
> This was missed in a previous patch for using new offload API.
>
> It turns out the line can be removed because that internal PMD
> crc_len data is not being used.
>
> Fixes: a922c6a789ff ("net/nfp: support new HW offloads API")
>
> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
Hi Alejandro,
Normally we are not getting non-critical fixes after this point, but to complete
offload API work and since this was requested fix, patch will be considered for
release, thanks.
next prev parent reply other threads:[~2018-05-23 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 10:14 Alejandro Lucero
2018-05-23 15:52 ` Ferruh Yigit [this message]
2018-05-24 13:22 ` 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=b29a8f34-98ab-f1e6-fcbf-08cdb6a2ddf4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.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).