All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	dev@dpdk.org, Ferruh Yigit <ferruh.yigit@amd.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [PATCH] doc: announce deprecation of RTE_CPUFLAG_NUMFLAGS
Date: Fri, 28 Jul 2023 12:11:00 +0200	[thread overview]
Message-ID: <2566913.Lt9SDvczpP@thomas> (raw)
In-Reply-To: <PAXPR04MB9328A7E4F5CC6D15F966AA8A8903A@PAXPR04MB9328.eurprd04.prod.outlook.com>

> > > > > To allow new cpu features to be added without ABI breakage,
> > > > > RTE_CPUFLAG_NUMFLAGS will be removed in DPDK 23.11 release.
> > > > >
> > > > > Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> > > >
> > > > +techboard,
> > > >
> > > > Request for review/ack, patch is to remove ABI restriction to add
> > > > new CPU flags.
> > >
> > > Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> > 
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied, thanks.




      reply	other threads:[~2023-07-28 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 10:18 [PATCH] doc: announce deprecation of RTE_CPUFLAG_NUMFLAGS Sivaprasad Tummala
2023-07-12 10:21 ` Ferruh Yigit
2023-07-12 14:51   ` Hemant Agrawal
2023-07-25  8:39 ` Ferruh Yigit
2023-07-25  8:40   ` Bruce Richardson
2023-07-25  9:24   ` Morten Brørup
2023-07-25  9:36   ` Kevin Traynor
2023-07-25 14:18   ` Tyler Retzlaff
2023-07-25 14:24     ` Jerin Jacob
2023-07-25 16:45       ` Hemant Agrawal
2023-07-28 10:11         ` Thomas Monjalon [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=2566913.Lt9SDvczpP@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinjacobk@gmail.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=sivaprasad.tummala@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.