From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>,
<stable@dpdk.org>, <maxime.coquelin@redhat.com>
Subject: Re: [PATCH v3 2/4] examples/vdpa: fix format overflow warning
Date: Wed, 19 Nov 2025 09:13:36 +0000 [thread overview]
Message-ID: <aR2KQKQhky7Dm-dh@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <5387340.ejJDZkT8p0@thomas>
On Wed, Nov 19, 2025 at 05:31:56AM +0100, Thomas Monjalon wrote:
> 15/11/2025 20:36, Stephen Hemminger:
> > +#define stringify(x) (#x)
> > +#define MAX_VDPA_STR_LEN sizeof(stringify(MAX_VDPA_SAMPLE_PORTS))
>
> Can you use RTE_STR?
>
+1 I had same comment on v2.
prev parent reply other threads:[~2025-11-19 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251110182209.104087-1-stephen@networkplumber.org>
2025-11-10 18:19 ` [PATCH 1/3] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-10 18:19 ` [PATCH 2/3] examples/vdpa: fix format overflow warning Stephen Hemminger
[not found] ` <20251111221857.443752-1-stephen@networkplumber.org>
2025-11-11 22:17 ` [PATCH v2 1/7] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-11 22:17 ` [PATCH v2 2/7] examples/vdpa: fix format overflow warning Stephen Hemminger
2025-11-14 15:59 ` Bruce Richardson
[not found] ` <20251115193749.101355-1-stephen@networkplumber.org>
2025-11-15 19:36 ` [PATCH v3 1/4] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-17 8:50 ` Bruce Richardson
2025-11-15 19:36 ` [PATCH v3 2/4] examples/vdpa: fix format overflow warning Stephen Hemminger
2025-11-19 4:31 ` Thomas Monjalon
2025-11-19 9:13 ` Bruce Richardson [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=aR2KQKQhky7Dm-dh@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).