patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>,
	Gregory Etelson <getelson@nvidia.com>,
	dev@dpdk.org
Cc: rasland@nvidia.com, stable@dpdk.org,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v2 1/2] net: fix GTP PSC headers
Date: Thu, 23 Jun 2022 14:53:41 +0300	[thread overview]
Message-ID: <80f33781-6fae-fdb8-e6fc-2bd48103d29c@oktetlabs.ru> (raw)
In-Reply-To: <b3ae1d75-0771-2972-8da3-fe6bce905f25@oktetlabs.ru>

On 6/23/22 14:38, Andrew Rybchenko wrote:
> On 6/21/22 16:45, Singh, Aman Deep wrote:
>> On 6/16/2022 11:31 PM, Gregory Etelson wrote:
>>> Fix bitmap fields order in little endian section of GTP PSC headers.
>>>
>>> Fixes: e8ca1479cdc4 ("net: add extension header for GTP PSC")
>>>
>>> cc: stable@dpdk.org
>>> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
>>> Reviewed-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>>
>> Acked-by: Aman Singh<aman.deep.singh@intel.com>
>>
> 
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>

Series applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2022-06-23 11:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  9:34 [PATCH " Gregory Etelson
2022-06-16  9:34 ` [PATCH 2/2] app/testpmd: fix GTP PSC raw processing Gregory Etelson
2022-06-16 18:01 ` [PATCH v2 1/2] net: fix GTP PSC headers Gregory Etelson
2022-06-16 18:01   ` [PATCH v2 2/2] app/testpmd: fix GTP PSC raw processing Gregory Etelson
2022-06-21 13:45   ` [PATCH v2 1/2] net: fix GTP PSC headers Singh, Aman Deep
2022-06-23 11:38     ` Andrew Rybchenko
2022-06-23 11:53       ` Andrew Rybchenko [this message]

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=80f33781-6fae-fdb8-e6fc-2bd48103d29c@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=getelson@nvidia.com \
    --cc=olivier.matz@6wind.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.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).