From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: Minutes of DPDK Technical Board Meeting, 2024-04-03
Date: Wed, 24 Apr 2024 21:10:06 +0200 [thread overview]
Message-ID: <4585113.cEBGB3zze1@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F3E4@smartserver.smartshare.dk>
24/04/2024 19:25, Morten Brørup:
> > Inlining should be avoided in public headers because of ABI
> > compatibility issue
> > and structures being exported because of inline requirement.
>
> This sounds like a techboard decision, which I don't think it was.
> Suggested wording:
>
> A disadvantage of inlining in public headers is ABI compatibility issues and structures being exported because of inline requirement.
>
>
> Perhaps I'm being paranoid, and the phrase "should be" already suffices.
>
> Whichever wording you prefer,
> ACK
This is the final report sent to dev@dpdk.org :)
Yes I think the word "should" reflect what was said
during the meeting without any formal vote.
prev parent reply other threads:[~2024-04-24 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 15:24 Minutes of DPDK Technical Board Meeting, 2024-04-03 Thomas Monjalon
2024-04-24 17:25 ` Morten Brørup
2024-04-24 19:10 ` 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=4585113.cEBGB3zze1@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=techboard@dpdk.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).