From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"alistair23@gmail.com" <alistair23@gmail.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"alistair.francis@wdc.com" <alistair.francis@wdc.com>
Subject: Re: [PATCH v3] asm-generic ABI: Allow statx syscall despite fstatat64, fstat64
Date: Tue, 25 Feb 2020 16:55:49 +0000 [thread overview]
Message-ID: <164d39b4-4d5b-a0a5-1939-af25e7eca47d@synopsys.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002251609090.25788@digraph.polyomino.org.uk>
On 2/25/20 8:10 AM, Joseph Myers wrote:
> On Mon, 24 Feb 2020, Vineet Gupta wrote:
>
>> Oh wait. Can we avoid this churn by simply undef __NR_fstat64 and __NR_fstatat64
>> from ARC sysdep.h ? And it will then automatically fallback to statx code !
>
> If all files needing this information include sysdep.h, that might well
> work.
I agree that this is a valid concern. If we really want to make it water tight we
could have the build system enforce this with -include or some such ?
prev parent reply other threads:[~2020-02-25 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 18:23 [PATCH] asm-generic ABI: Allow statx syscall despite fstatat64,fstat64 Vineet Gupta
2020-02-24 18:39 ` Florian Weimer
2020-02-24 19:03 ` Vineet Gupta
2020-02-24 19:13 ` Florian Weimer
2020-02-24 19:27 ` Vineet Gupta
2020-02-24 19:38 ` Florian Weimer
2020-02-24 22:15 ` [PATCH v2] " Vineet Gupta
2020-02-25 0:09 ` Joseph Myers
2020-02-25 0:29 ` [PATCH v3] " Vineet Gupta
2020-02-25 3:13 ` [PATCH v3] asm-generic ABI: Allow statx syscall despite fstatat64, fstat64 Vineet Gupta
2020-02-25 16:10 ` Joseph Myers
2020-02-25 16:55 ` Vineet Gupta [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164d39b4-4d5b-a0a5-1939-af25e7eca47d@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).