From: David Marchand <david.marchand@redhat.com>
To: Ankur Dwivedi <adwivedi@marvell.com>
Cc: dev <dev@dpdk.org>, Anoob Joseph <anoobj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [PATCH 0/2] fix compilation with GCC 12
Date: Fri, 17 Jun 2022 13:36:53 +0200 [thread overview]
Message-ID: <CAJFAV8xO0RGQNQp4zkPk-unx9+EXe-ciXUo8Y6UXVX-XvDHv0w@mail.gmail.com> (raw)
In-Reply-To: <20220617061432.2685-1-adwivedi@marvell.com>
On Fri, Jun 17, 2022 at 8:15 AM Ankur Dwivedi <adwivedi@marvell.com> wrote:
>
> This patch series resolves compilation warning observed with GCC 12,
> in common/cpt and crypto/cnxk.
>
> Ankur Dwivedi (2):
> common/cpt: fix compilation with GCC 12
> crypto/cnxk: fix compilation with GCC 12
>
Two small nits in commitlogs that can be fixed while merging: no need
for an empty line between Fixes: and Cc:.
For the series,
Tested-by: David Marchand <david.marchand@redhat.com>
Thanks Ankur.
--
David Marchand
next prev parent reply other threads:[~2022-06-17 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 6:14 Ankur Dwivedi
2022-06-17 6:14 ` [PATCH 1/2] common/cpt: " Ankur Dwivedi
2022-06-17 12:07 ` David Marchand
2022-06-17 12:39 ` [EXT] " Ankur Dwivedi
2022-06-17 6:14 ` [PATCH 2/2] crypto/cnxk: " Ankur Dwivedi
2022-06-17 11:36 ` David Marchand [this message]
2022-06-17 13:39 ` [PATCH v2 0/2] " Ankur Dwivedi
2022-06-17 13:39 ` [PATCH v2 1/2] common/cpt: " Ankur Dwivedi
2022-06-17 13:39 ` [PATCH v2 2/2] crypto/cnxk: " Ankur Dwivedi
2022-06-20 9:08 ` [PATCH v2 0/2] " Akhil Goyal
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=CAJFAV8xO0RGQNQp4zkPk-unx9+EXe-ciXUo8Y6UXVX-XvDHv0w@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.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).