DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [PATCH v3] build: announce requirement for C11
Date: Fri, 28 Jul 2023 11:34:39 +0200	[thread overview]
Message-ID: <5851212.MhkbZ0Pkbq@thomas> (raw)
In-Reply-To: <CALBAE1Pd75oemwJCcgs43kJHmSdU5C192At8W+U_rrsSTKFFMg@mail.gmail.com>

20/07/2023 12:56, Jerin Jacob:
> On Thu, Jul 20, 2023 at 1:52 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Wed, May 17, 2023 at 06:34:00PM +0100, Bruce Richardson wrote:
> > > Add a deprecation notice informing users that we will require a C11
> > > compiler from 23.11 release onwards. This requirement was agreed by
> > > technical board to enable use of newer C language features, e.g.
> > > standard atomics. [1]
> > >
> > > [1] http://inbox.dpdk.org/dev/DBAPR08MB58148CEC3E1454E8848A938998AB9@DBAPR08MB5814.eurprd08.prod.outlook.com/
> > >
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> > >
> > > ---
> > >
> > > V3:
> > > - add additional detail following discussion on-list
> > >
> > > V2:
> > > - add requirement for stdatomics
> > > - fix sphinx formatting
> > > ---
> > >  doc/guides/rel_notes/deprecation.rst | 18 ++++++++++++++++++
> > >  1 file changed, 18 insertions(+)
> > >
> > Ping for additional review/acks and merge.
> 
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

> > This deprecation notice really needs to go into 23.07 to allow the C11
> > requirement to be met in 23.11!

Applied, thanks.



      reply	other threads:[~2023-07-28  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 15:14 [PATCH] " Bruce Richardson
2023-05-03 15:35 ` Tyler Retzlaff
2023-05-03 15:37   ` Bruce Richardson
2023-05-03 15:39 ` Ferruh Yigit
2023-05-03 15:45   ` Tyler Retzlaff
2023-05-03 15:57   ` Bruce Richardson
2023-05-03 16:07     ` Tyler Retzlaff
2023-05-03 16:51     ` Ferruh Yigit
2023-05-03 17:30 ` [PATCH v2] " Bruce Richardson
2023-05-04  7:50   ` Mattias Rönnblom
2023-05-04  8:48     ` Bruce Richardson
2023-05-04 15:24       ` Tyler Retzlaff
2023-05-03 21:34 ` [PATCH] " Morten Brørup
2023-05-17 17:34 ` [PATCH v3] " Bruce Richardson
2023-05-19 12:19   ` Aaron Conole
2023-05-19 20:01     ` Tyler Retzlaff
2023-07-20  8:22   ` Bruce Richardson
2023-07-20 10:56     ` Jerin Jacob
2023-07-28  9:34       ` 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=5851212.MhkbZ0Pkbq@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinjacobk@gmail.com \
    --cc=roretzla@linux.microsoft.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).