patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Pavel Belous <Pavel.Belous@aquantia.com>,
	 "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 09/10] net/atlantic: fix missing VLAN filter offload
Date: Tue, 12 Mar 2019 22:03:54 +0200	[thread overview]
Message-ID: <CAHLOa7RKj1LVnKSnKESOb_r-n=tO+H_U2S8xzUVOQS2wiDZPcQ@mail.gmail.com> (raw)
In-Reply-To: <fbb78b3dabc2652be3e43e2c8feaf1e37620ee4e.1552402263.git.igor.russkikh@aquantia.com>

Original vlan offload code declared callbacks, but did not
> enable the feature offload bit
>
> Cc: stable@dpdk.org
> Fixes: f7c2c2c8c558 ("net/atlantic: implement VLAN filters and offloads")
> Signed-off-by: Igor Russkikh <igor.russkikh@aquantia.com>
> ---
> Reviewed-by: Rami Rosen <ramirose@gmail.com>



>
>

  reply	other threads:[~2019-03-12 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1552402263.git.igor.russkikh@aquantia.com>
2019-03-12 15:24 ` [dpdk-stable] [PATCH v3 01/10] net/atlantic: fix negative error codes Igor Russkikh
2019-03-12 15:24 ` [dpdk-stable] [PATCH v3 04/10] net/atlantic: fix buffer overflow Igor Russkikh
2019-03-12 15:25 ` [dpdk-stable] [PATCH v3 06/10] net/atlantic: fix EEPROM get for small and uneven lengths Igor Russkikh
2019-03-12 15:25 ` [dpdk-stable] [PATCH v3 07/10] net/atlantic: fix link configuration Igor Russkikh
2019-03-12 15:25 ` [dpdk-stable] [PATCH v3 09/10] net/atlantic: fix missing VLAN filter offload Igor Russkikh
2019-03-12 20:03   ` Rami Rosen [this message]
2019-03-12 15:25 ` [dpdk-stable] [PATCH v3 10/10] net/atlantic: fix xstats to return correct number of items Igor Russkikh

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='CAHLOa7RKj1LVnKSnKESOb_r-n=tO+H_U2S8xzUVOQS2wiDZPcQ@mail.gmail.com' \
    --to=ramirose@gmail.com \
    --cc=Igor.Russkikh@aquantia.com \
    --cc=Pavel.Belous@aquantia.com \
    --cc=dev@dpdk.org \
    --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).