patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: stable@dpdk.org, Ophir Munk <ophirmu@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH v1] net/mlx4: fix CRC stripping capability report
Date: Mon, 30 Apr 2018 15:47:51 +0200	[thread overview]
Message-ID: <3736968.MDDTzanQ13@xps> (raw)
In-Reply-To: <1525095746.23337.19.camel@debian.org>

30/04/2018 15:42, Luca Boccassi:
> On Mon, 2018-04-30 at 12:23 +0000, Ophir Munk wrote:
> > There are two capabilities related to CRC stripping:
> > 1. mlx4 HW capability to perform CRC stripping on a recieved packet.
> > This capability is built in mlx4 HW. It should be returned by the API
> > call mlx4_get_rx_queue_offloads().
> > 2. mlx4 driver capability to enable/disable HW CRC stripping. This
> > capability is dependent on the driver version.
> > Before this commit the seccond capability was falsely returned by
> > the mentioned API. This commit fixes it by returning the first
> > capability.
> > 
> > Fixes: de1df14e6e6ec ("net/mlx4: support CRC strip toggling")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
> 
> Has this or a version of this fix been committed to mainline?

I think it is a duplicate.
A new patch has been sent to dpdk-dev + dpdk-stable.

  reply	other threads:[~2018-04-30 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 12:23 Ophir Munk
2018-04-30 13:42 ` Luca Boccassi
2018-04-30 13:47   ` Thomas Monjalon [this message]
2018-04-30 12:25 Ophir Munk
2018-05-03  5:47 ` Shahaf Shuler

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=3736968.MDDTzanQ13@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=ophirmu@mellanox.com \
    --cc=stable@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).