From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: dev@dpdk.org, "De Lara Guarch,
Pablo" <pablo.de.lara.guarch@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] hash: validate hash bucket entries while compiling
Date: Fri, 13 Jul 2018 23:40:09 +0200 [thread overview]
Message-ID: <6777404.RLFGYKfp85@xps> (raw)
In-Reply-To: <VI1PR0801MB19369EE5301D319BB8E4D20098580@VI1PR0801MB1936.eurprd08.prod.outlook.com>
13/07/2018 22:20, Honnappa Nagarahalli:
> Hi Pablo,
> Thank you for your response. I recently noticed this macro 'RTE_BUILD_BUG_ON'. Does it make sense to use this macro instead (though the error message will be more cryptic)?
Yes, I've hesitated to suggest RTE_BUILD_BUG_ON,
but decided to push your #error solution which should be fine.
prev parent reply other threads:[~2018-07-13 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 15:30 Honnappa Nagarahalli
2018-07-12 7:42 ` Thomas Monjalon
2018-07-12 8:05 ` De Lara Guarch, Pablo
2018-07-12 10:43 ` Thomas Monjalon
2018-07-13 20:20 ` Honnappa Nagarahalli
2018-07-13 21:40 ` 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=6777404.RLFGYKfp85@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.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).