From: Bruce Richardson <bruce.richardson@intel.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: <dev@dpdk.org>, <mb@smartsharesystems.com>
Subject: Re: [PATCH v5 2/3] net/intel: use portable version of __builtin_add_overflow
Date: Fri, 14 Mar 2025 14:46:21 +0000 [thread overview]
Message-ID: <Z9RBPQ1W3z4pG5x6@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1741962820-27123-3-git-send-email-andremue@linux.microsoft.com>
On Fri, Mar 14, 2025 at 07:33:39AM -0700, Andre Muezerie wrote:
> __builtin_add_overflow is gcc specific. It should be replaced with
> a portable version that can also be used with other compilers.
>
> Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2025-03-14 14:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 22:32 [PATCH 0/5] add " Andre Muezerie
2025-01-02 22:32 ` [PATCH 1/5] maintainers: " Andre Muezerie
2025-01-02 22:32 ` [PATCH 2/5] lib/eal: " Andre Muezerie
2025-01-03 8:19 ` Morten Brørup
2025-01-03 20:38 ` Andre Muezerie
2025-01-02 22:32 ` [PATCH 3/5] doc/api: " Andre Muezerie
2025-01-02 22:32 ` [PATCH 4/5] drivers/net: use " Andre Muezerie
2025-01-02 22:32 ` [PATCH 5/5] app/test: add tests for portable versions " Andre Muezerie
2025-01-02 23:51 ` [PATCH 0/5] add portable version " Stephen Hemminger
2025-01-03 0:15 ` Andre Muezerie
2025-01-03 0:41 ` Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 " Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 1/5] maintainers: " Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 2/5] lib/eal: " Andre Muezerie
2025-01-06 11:07 ` Bruce Richardson
2025-01-06 11:21 ` Morten Brørup
2025-01-06 11:34 ` Bruce Richardson
2025-01-06 11:58 ` Morten Brørup
2025-03-05 15:46 ` Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 3/5] doc/api: " Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 4/5] drivers/net: use " Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 5/5] app/test: add tests for " Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 0/5] add " Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 1/5] maintainers: " Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 2/5] eal: " Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 3/5] doc/api: " Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 4/5] net/intel: use " Andre Muezerie
2025-03-05 16:52 ` Bruce Richardson
2025-03-11 18:39 ` Andre Muezerie
2025-03-05 16:38 ` [PATCH v3 5/5] app/test: add tests for " Andre Muezerie
2025-03-06 3:00 ` Patrick Robb
2025-03-13 20:00 ` [PATCH v4 0/5] add " Andre Muezerie
2025-03-13 20:00 ` [PATCH v4 1/5] maintainers: " Andre Muezerie
2025-03-14 8:39 ` Bruce Richardson
2025-03-13 20:00 ` [PATCH v4 2/5] eal: " Andre Muezerie
2025-03-13 20:00 ` [PATCH v4 3/5] doc/api: " Andre Muezerie
2025-03-14 8:40 ` Bruce Richardson
2025-03-13 20:00 ` [PATCH v4 4/5] net/intel: use " Andre Muezerie
2025-03-13 20:00 ` [PATCH v4 5/5] app/test: add tests for " Andre Muezerie
2025-03-14 14:33 ` [PATCH v5 0/3] add " Andre Muezerie
2025-03-14 14:33 ` [PATCH v5 1/3] eal: " Andre Muezerie
2025-03-14 14:33 ` [PATCH v5 2/3] net/intel: use " Andre Muezerie
2025-03-14 14:46 ` Bruce Richardson [this message]
2025-03-14 14:33 ` [PATCH v5 3/3] app/test: add tests for " Andre Muezerie
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=Z9RBPQ1W3z4pG5x6@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=andremue@linux.microsoft.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).