From: Arnout Vandecappelle <arnout@mind.be>
To: Alsey Coleman Miller <alseycmiller@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/libdispatch: add fix for 32-bit arm
Date: Mon, 6 Feb 2023 12:26:36 +0100 [thread overview]
Message-ID: <c155387a-3cba-db3e-9931-326d8b7e8ff0@mind.be> (raw)
In-Reply-To: <20220329185059.943889-3-alseycmiller@gmail.com>
Hi Alsey,
This patch should be included in the first one.
On 29/03/2022 20:50, Alsey Coleman Miller wrote:
> Signed-off-by: Alsey Coleman Miller <alseycmiller@gmail.com>
> ---
> package/libdispatch/arm-yield.patch | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
> create mode 100644 package/libdispatch/arm-yield.patch
>
> diff --git a/package/libdispatch/arm-yield.patch b/package/libdispatch/arm-yield.patch
> new file mode 100644
> index 0000000000..fa7cf7cce4
> --- /dev/null
> +++ b/package/libdispatch/arm-yield.patch
> @@ -0,0 +1,13 @@
Patches should be git formatted. They should have a full commit message that
explains the issue, and a Signed-off-by. There should also be an upstream
reference, or something like "Not applicable" and an explaantion why it's not
applicable for upstream.
Regards,
Arnout
> +diff --git a/src/shims/yield.c b/src/shims/yield.c
> +index 43f0017..d0c5fff 100644
> +--- a/src/shims/yield.c
> ++++ b/src/shims/yield.c
> +@@ -36,7 +36,7 @@ void *
> + _dispatch_wait_for_enqueuer(void **ptr)
> + {
> + #if !DISPATCH_HW_CONFIG_UP
> +-#if defined(__arm__) || defined(__arm64__)
> ++#if (defined(__arm__) && defined(__APPLE__)) || defined(__arm64__)
> + int spins = DISPATCH_WAIT_SPINS_WFE;
> + void *value;
> + while (unlikely(spins-- > 0)) {
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-06 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 18:50 [Buildroot] [PATCH 1/4] package/pkg-cmake: allow overriding toolchain Alsey Coleman Miller
2022-03-29 18:50 ` [Buildroot] [PATCH 2/4] package/libdispatch: add libdispatch package Alsey Coleman Miller
2022-03-29 18:50 ` [Buildroot] [PATCH 3/4] package/libdispatch: add fix for 32-bit arm Alsey Coleman Miller
2023-02-06 11:26 ` Arnout Vandecappelle [this message]
2022-03-29 18:50 ` [Buildroot] [PATCH 4/4] DEVELOPERS: add Alsey Miller for libdispatch Alsey Coleman Miller
2022-03-29 19:17 ` [Buildroot] [PATCH 1/4] package/pkg-cmake: allow overriding toolchain Alsey Miller
2022-03-29 19:26 ` James Hilliard
2022-03-29 19:58 ` Alsey Miller
2022-03-29 20:10 ` James Hilliard
2022-03-29 23:19 ` Alsey Miller
2022-06-20 23:14 ` James Hilliard
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=c155387a-3cba-db3e-9931-326d8b7e8ff0@mind.be \
--to=arnout@mind.be \
--cc=alseycmiller@gmail.com \
--cc=buildroot@buildroot.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