From: Peter Korsgaard <peter@korsgaard.com>
To: Petr Vorel <pevik@seznam.cz>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ltp-testsuite: build getcontext01.c on musl
Date: Fri, 30 Sep 2022 17:10:17 +0200 [thread overview]
Message-ID: <87sfk8525i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220902221936.969471-1-pevik@seznam.cz> (Petr Vorel's message of "Sat, 3 Sep 2022 00:19:36 +0200")
>>>>> "Petr" == Petr Vorel <pevik@seznam.cz> writes:
> From: Petr Vorel <petr.vorel@gmail.com>
> It was fixed for musl during conversion to the new API in 0f519d0da
> (released in 20220527).
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
Committed to 2022.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-30 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 22:19 [Buildroot] [PATCH 1/1] package/ltp-testsuite: build getcontext01.c on musl Petr Vorel
2022-09-24 8:31 ` Thomas Petazzoni
2022-09-30 15:10 ` Peter Korsgaard [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=87sfk8525i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=pevik@seznam.cz \
/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).