From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] net: improve vlan header type alignment
Date: Thu, 17 Oct 2024 22:44:23 +0200 [thread overview]
Message-ID: <7686686.jRhZ6ZUK3Y@thomas> (raw)
In-Reply-To: <20241013083554.97489-1-mb@smartsharesystems.com>
13/10/2024 10:35, Morten Brørup:
> +static_assert(sizeof(struct rte_ether_addr) == 6,
> + "sizeof(struct rte_ether_addr) == 6");
> +static_assert(alignof(struct rte_ether_addr) == 2,
> + "alignof(struct rte_ether_addr) == 2");
Instead of repeating the condition twice,
it would be simpler to use RTE_BUILD_BUG_ON
next prev parent reply other threads:[~2024-10-17 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 8:35 Morten Brørup
2024-10-13 8:51 ` Morten Brørup
2024-10-14 5:42 ` fengchengwen
2024-10-14 8:04 ` Bruce Richardson
2024-10-17 20:44 ` Thomas Monjalon [this message]
2024-10-17 23:41 ` Morten Brørup
2024-10-18 9:11 ` Thomas Monjalon
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=7686686.jRhZ6ZUK3Y@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).