patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Conor Walsh <conor.walsh@intel.com>
Cc: bruce.richardson@intel.com, ajit.khaparde@broadcom.com,
	somnath.kotur@broadcom.com, bluca@debian.org,
	stuart.schacher@broadcom.com, venkatkumar.duvvuru@broadcom.com,
	michael.wildt@broadcom.com, stable@dpdk.org, dev@dpdk.org,
	linglix.chen@intel.com, david.marchand@redhat.com
Subject: Re: [dpdk-stable] [PATCH v3 0/2] build: add Wformat to fix gcc compile warnings and format fixes
Date: Sun, 22 Nov 2020 21:07:48 +0100	[thread overview]
Message-ID: <3594322.kmZJcSPU1q@thomas> (raw)
In-Reply-To: <20201119101700.3869583-1-conor.walsh@intel.com>

19/11/2020 11:16, Conor Walsh:
> On some systems Wformat-nonliteral and Wformat-security could not be
> checked without Wformat also being specified this causes a compile
> warning on these systems. This patchset adds Wformat to
> config/meson.build and fixes some format issues that this exposed.
> 
> ---
> 
> v3: add stable@dpdk.org to cc list following list feedback

The Cc: stable@dpdk.org must be part of the commit log.
Please at other patches (and contributors guidelines) for inspiration.

Series applied, thanks.



      parent reply	other threads:[~2020-11-22 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201118181103.3865787-1-conor.walsh@intel.com>
2020-11-19 10:16 ` Conor Walsh
2020-11-19 10:16   ` [dpdk-stable] [PATCH v3 1/2] build: fix gcc compile warnings by adding wformat Conor Walsh
2020-11-20  7:23     ` Chen, LingliX
2020-11-19 10:17   ` [dpdk-stable] [PATCH v3 2/2] net/bnxt: fix format characters for unsigned values Conor Walsh
2020-11-19 23:12     ` Ajit Khaparde
2020-11-22 20:07   ` 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=3594322.kmZJcSPU1q@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=linglix.chen@intel.com \
    --cc=michael.wildt@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=stuart.schacher@broadcom.com \
    --cc=venkatkumar.duvvuru@broadcom.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).