From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org, Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH v2 0/3] add __extension__ keyword to statement expressions
Date: Fri, 16 Feb 2024 18:04:03 +0100 [thread overview]
Message-ID: <CAJFAV8wn51ZzOC6cLUSVEX8W9n+iOmncwi+MLj3gMqMQmYbkyQ@mail.gmail.com> (raw)
In-Reply-To: <20240216102454.4156609-1-david.marchand@redhat.com>
On Fri, Feb 16, 2024 at 11:25 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> Tyler explained in v1:
> """
> As requested from previous rejected series this series applies the
> __extension__ keyword to all statement expressionsin DPDK.
> """
>
> Changes since v1:
> - rebased,
> - added two cleanups before Tyler patch,
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-02-16 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 23:02 [PATCH 0/4] " Tyler Retzlaff
2023-11-15 23:02 ` [PATCH 1/4] lib: add extension " Tyler Retzlaff
2023-11-15 23:02 ` [PATCH 2/4] app: " Tyler Retzlaff
2023-11-15 23:02 ` [PATCH 3/4] drivers: " Tyler Retzlaff
2023-11-20 7:42 ` Ruifeng Wang
2023-11-15 23:02 ` [PATCH 4/4] examples: " Tyler Retzlaff
2024-02-16 10:24 ` [PATCH v2 0/3] add __extension__ " David Marchand
2024-02-16 10:24 ` [PATCH v2 1/3] eal: add helper to skip whitespaces David Marchand
2024-02-16 10:27 ` David Marchand
2024-02-16 10:39 ` Bruce Richardson
2024-02-16 10:24 ` [PATCH v2 2/3] drivers: use common min/max macros David Marchand
2024-02-19 1:37 ` Xu, Rosen
2024-02-19 2:13 ` Ajit Khaparde
2024-02-16 10:24 ` [PATCH v2 3/3] add extension keyword to GCC statement expressions David Marchand
2024-02-18 3:07 ` fengchengwen
2024-02-16 17:04 ` David Marchand [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=CAJFAV8wn51ZzOC6cLUSVEX8W9n+iOmncwi+MLj3gMqMQmYbkyQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).