From: Thomas Monjalon <thomas@monjalon.net>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, "Jerin Jacob" <jerinj@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
david.marchand@redhat.com,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v2] eal: provide macro to allocate and name a section or segment
Date: Tue, 13 Feb 2024 12:28:02 +0100 [thread overview]
Message-ID: <15015499.uLZWGnKmhe@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F20A@smartserver.smartshare.dk>
13/02/2024 09:51, Morten Brørup:
> > From: Tyler Retzlaff [mailto:roretzla@linux.microsoft.com]
> > Sent: Monday, 12 February 2024 21.52
> >
> > Provide __rte_section(name) macro that allocates and names a section
> > or segment that works with both MSVC and GCC.
> >
> > Update RTE_TRACE_POINT_REGISTER with __rte_section("__rte_trace_point")
> > instead of __attribute__(section(name)) so the macro may be compatibly
> > expanded when using MSVC.
> >
> > Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> > ---
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
Applied (with minor nits fixed), thanks.
prev parent reply other threads:[~2024-02-13 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 22:47 [PATCH] eal: provide trace point register macro for MSVC Tyler Retzlaff
2023-11-06 16:40 ` Thomas Monjalon
2023-11-06 17:30 ` Tyler Retzlaff
2023-11-12 12:04 ` Thomas Monjalon
2024-02-12 20:51 ` [PATCH v2] eal: provide macro to allocate and name a section or segment Tyler Retzlaff
2024-02-13 8:51 ` Morten Brørup
2024-02-13 11:28 ` 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=15015499.uLZWGnKmhe@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=roretzla@linux.microsoft.com \
--cc=skori@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.