From: Joseph Myers <joseph@codesourcery.com>
To: Matheus Castanho <msc@linux.ibm.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 01/15] linux: Add pidfd_open
Date: Wed, 1 Jun 2022 22:22:15 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2206012221040.3755786@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87tu942jbf.fsf@linux.ibm.com>
On Wed, 1 Jun 2022, Matheus Castanho via Libc-alpha wrote:
> I don't think there's much else to do besides returning UNSUPPORTED. Of
> course this will mark the test as UNSUPPORTED for any failure in the
> internal gcc call, but I don't see it as a problem today since this
> function seems to be used only for macro processing.
I *do* think it's a problem to return UNSUPPORTED if the compilation fails
unexpectedly with current kernel headers. However, it would be OK to
hardcode a minimum kernel headers version below which the test is
UNSUPPORTED.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-06-01 22:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 17:44 [PATCH v2 00/15] linux: Add new syscalls Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 01/15] linux: Add pidfd_open Adhemerval Zanella
2022-05-16 21:12 ` Carlos O'Donell
2022-06-01 18:02 ` Matheus Castanho
2022-06-01 18:49 ` Adhemerval Zanella
2022-06-01 20:53 ` Matheus Castanho
2022-06-01 22:22 ` Joseph Myers [this message]
2022-02-07 17:44 ` [PATCH v2 02/15] linux: Add pidfd_getfd Adhemerval Zanella
2022-05-16 21:12 ` Carlos O'Donell
2022-02-07 17:44 ` [PATCH v2 03/15] linux: Add pidfd_send_signal Adhemerval Zanella
2022-05-16 21:12 ` Carlos O'Donell
2022-02-07 17:44 ` [PATCH v2 04/15] linux: Add P_PIDFD Adhemerval Zanella
2022-05-16 21:12 ` Carlos O'Donell
2022-02-07 17:44 ` [PATCH v2 05/15] linux: Add tst-pidfd.c Adhemerval Zanella
2022-05-16 21:12 ` Carlos O'Donell
2022-02-07 17:44 ` [PATCH v2 06/15] linux: Add process_madvise Adhemerval Zanella
2022-05-31 22:03 ` Carlos O'Donell
2022-06-01 18:04 ` Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 07/15] linux: Add process_mrelease Adhemerval Zanella
2022-05-31 22:12 ` Carlos O'Donell
2022-06-01 18:35 ` Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 08/15] linux: Add fsopen Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 09/15] linux: Add fsmount Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 10/15] linux: Add move_mount Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 11/15] linux: Add fsconfig Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 12/15] linux: Add fspick Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 13/15] linux: Add open_tree Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 14/15] linux: Add tst-mount to check for Linux new mount API Adhemerval Zanella
2022-02-07 17:44 ` [PATCH v2 15/15] linux: Add mount_setattr Adhemerval Zanella
2022-05-16 21:12 ` [PATCH v2 00/15] linux: Add new syscalls Carlos O'Donell
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=alpine.DEB.2.22.394.2206012221040.3755786@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).