From: Peter Korsgaard <peter@korsgaard.com>
To: Scott Fan <fancp2007@gmail.com>
Cc: buildroot@buildroot.org, thomas.petazzoni@bootlin.com
Subject: Re: [Buildroot] [PATCH] package/procps-ng: fix pidfd_open checking
Date: Sat, 07 Dec 2024 10:47:53 +0100 [thread overview]
Message-ID: <877c8b4yeu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <871pym9ifa.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Thu, 05 Dec 2024 17:57:29 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Scott" == Scott Fan <fancp2007@gmail.com> writes:
>> The previous build setup would check for pidfd_open using
>> AC_CHECK_FUNC and would be incorrectly reported as true.
>> Backport patch from upstream:
>> [1] https://gitlab.com/procps-ng/procps/-/commit/2507bc475782ff5e0541d37c780dff1e293c9553
>> [2] https://gitlab.com/procps-ng/procps/-/commit/587efb47df7ddbfda4e6abdd1e7792a2531a238f
>> [3] https://gitlab.com/procps-ng/procps/-/commit/5acbb5dc1587d688de646d739a97251eb893bbb0
>> Signed-off-by: Scott Fan <fancp2007@gmail.com>
> Committed after adding a reference to an autobuilder failure, thanks.
Committed to 2024.02.x and 2024.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-12-07 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 0:20 [Buildroot] [PATCH] package/procps-ng: fix pidfd_open checking Scott Fan
2024-10-31 18:18 ` Thomas Petazzoni via buildroot
2024-11-01 1:31 ` Scott Fan
2024-11-04 13:23 ` Scott Fan
2024-11-24 16:29 ` Thomas Petazzoni via buildroot
2024-11-26 1:50 ` Scott Fan
2024-11-26 13:57 ` Thomas Petazzoni via buildroot
2024-11-27 0:35 ` Scott Fan
2024-11-27 1:01 ` Scott Fan
2024-11-27 7:44 ` Thomas Petazzoni via buildroot
2024-11-28 3:50 ` Scott Fan
2024-12-05 16:57 ` Peter Korsgaard
2024-12-07 9:47 ` 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=877c8b4yeu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fancp2007@gmail.com \
--cc=thomas.petazzoni@bootlin.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.