DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
	Gregory Etelson <getelson@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Gregory Etelson <getelson@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH] net: announce changes in IPv4 header
Date: Mon, 2 Aug 2021 12:38:40 +0000	[thread overview]
Message-ID: <CO6PR18MB4484B7719D4EBA3BA097DB18D8EF9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB3753B710DCBECFE2E7E6B5C3DFEF9@DM6PR12MB3753.namprd12.prod.outlook.com>

> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Gregory Etelson
> > Sent: Monday, August 2, 2021 13:39
> > To: dev@dpdk.org
> > Cc: Gregory Etelson <getelson@nvidia.com>; Matan Azrad
> > <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Ori Kam
> > <orika@nvidia.com>; Ray Kinsella <mdr@ashroe.eu>
> > Subject: [dpdk-dev] [PATCH] net: announce changes in IPv4 header
> >
> > Announce changes to add 2 unions. The first union will provide integral and
> > bits access to version and IHL. The second union will provide integral and
> bits
> > access to fragment flags and offset.
> >
> > Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Acked-by: Akhil Goyal <gakhil@marvell.com>


  reply	other threads:[~2021-08-02 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 10:38 Gregory Etelson
2021-08-02 10:42 ` Andrew Rybchenko
2021-08-02 12:10 ` Slava Ovsiienko
2021-08-02 12:38   ` Akhil Goyal [this message]
2021-08-03 18:06     ` Ajit Khaparde
2021-08-04 14:27       ` Thomas Monjalon

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=CO6PR18MB4484B7719D4EBA3BA097DB18D8EF9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=mdr@ashroe.eu \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --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).