DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>,
	<techboard@dpdk.org>
Subject: RE: [PATCH] build: announce requirement for C11
Date: Wed, 3 May 2023 23:34:52 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D878E2@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230503151413.14915-1-bruce.richardson@intel.com>

> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Wednesday, 3 May 2023 17.14
> 
> 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@DBAPR08
> MB5814.eurprd08.prod.outlook.com/
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Acked-by: Morten Brørup <mb@smartsharesystems.com>


  parent reply	other threads:[~2023-05-03 21:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 15:14 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 ` Morten Brørup [this message]
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

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=98CBD80474FA8B44BF855DF32C47DC35D878E2@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=techboard@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).