patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Wei Zhao <wei.zhao1@intel.com>, ferruh.yigit@intel.com
Cc: stable@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-stable] [PATCH] net/ixgbe: remove hardcoded CRC STRIP config from ixgbe
Date: Tue, 24 Jul 2018 09:16:35 +0100	[thread overview]
Message-ID: <1532420195.20916.5.camel@debian.org> (raw)
In-Reply-To: <1532399341-51650-1-git-send-email-wei.zhao1@intel.com>

On Tue, 2018-07-24 at 10:29 +0800, Wei Zhao wrote:
> There are CRC related ifdefs for ixgbe:
> CONFIG_RTE_LIBRTE_IXGBE_PF_DISABLE_STRIP_CRC=n
> These are used in VF drivers ixgbevf_dev_configure() functions.
> VF cannot change the CRC strip behavior and based on what PF
> configured it needs to response proper to user
> ixgbevf_dev_configure()request. Right now what PF set is
> defined by above config options but this method is too static.
> 
> Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
>  app/test-pmd/parameters.c        |  6 ++++++
>  app/test-pmd/testpmd.c           |  2 ++
>  app/test-pmd/testpmd.h           |  1 +
>  drivers/net/ixgbe/ixgbe_ethdev.c | 20 ++++++++++----------
>  lib/librte_ethdev/rte_ethdev.h   |  1 +
>  5 files changed, 20 insertions(+), 10 deletions(-)

Hi,

For which stable release branch is this patch intended? Has it (or an
equivalent) been merged into mainline?

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-07-24  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  2:29 Wei Zhao
2018-07-24  8:16 ` Luca Boccassi [this message]
2018-07-24  2:36 Wei Zhao
2018-08-09  8:31 ` Ferruh Yigit
2018-08-12  6:28   ` Shahaf Shuler
2018-08-12  7:52     ` Andrew Rybchenko
2018-08-12  8:46       ` Shahaf Shuler
2018-08-13 15:10         ` 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=1532420195.20916.5.camel@debian.org \
    --to=bluca@debian.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=wei.zhao1@intel.com \
    --cc=wenzhuo.lu@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).