From: "Arnd Bergmann" <arnd@arndb.de>
To: "Willy Tarreau" <w@1wt.eu>,
"chris.chenfeiyang" <chris.chenfeiyang@gmail.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
"Feiyang Chen" <chenfeiyang@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] nolibc: Add statx() support to implement sys_stat()
Date: Wed, 08 Feb 2023 08:29:47 +0100 [thread overview]
Message-ID: <17740a63-624f-47da-a701-dd218f95f9da@app.fastmail.com> (raw)
In-Reply-To: <Y+MXk9A+gB1W6T/n@1wt.eu>
On Wed, Feb 8, 2023, at 04:31, Willy Tarreau wrote:
> On Wed, Feb 08, 2023 at 10:09:48AM +0800, Feiyang Chen wrote:
>> On Tue, 7 Feb 2023 at 22:31, Arnd Bergmann <arnd@arndb.de> wrote:
> (...)
>> > Given that all architectures implement statx the same way, I wonder
>> > if we can't just kill off the old function here and always use statx.
>> >
>> > That would also allow removing the architecture specific
>> > sys_stat_struct definitions in all arch-*.h files.
>> >
>>
>> Hi, Arnd,
>>
>> I'd really like to make all architectures use sys_statx() instead
>> of sys_stat(). I just fear we might get dragged into a long discussion.
>> Can I send a patch series to do this later?
>
> I generally agree with the Arnd's points overall and I'm fine with the
> rest of your series. On this specific point, I'm fine with your proposal,
> let's just start with sys_statx() only on this arch, please add a comment
> about this possibility in the commit message that brings statx(),
> indicating that other archs are likely to benefit from it as well, and
> let's see after this if we can migrate all archs to statx.
Ok, makes sense. Just change the description then to note that this
will also fix riscv32 (which has only statx) as well as arc, hexagon,
nios2 and openrisc (which have statx and stat64 but not stat or newstat).
Arnd
next prev parent reply other threads:[~2023-02-08 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 2:09 [PATCH 0/3] Add LoongArch support to nolibc chris.chenfeiyang
2023-02-07 2:09 ` [PATCH 1/3] nolibc: Add statx() support to implement sys_stat() chris.chenfeiyang
2023-02-07 14:30 ` Arnd Bergmann
2023-02-08 2:09 ` Feiyang Chen
2023-02-08 3:31 ` Willy Tarreau
2023-02-08 7:29 ` Arnd Bergmann [this message]
2023-02-08 7:42 ` Feiyang Chen
2023-02-08 8:06 ` Arnd Bergmann
2023-02-08 8:19 ` Willy Tarreau
2023-02-08 9:20 ` Feiyang Chen
[not found] ` <d0df35466db74097b8e70e28d35a4776@AcuMS.aculab.com>
2023-02-08 14:07 ` Willy Tarreau
2023-02-08 8:07 ` Willy Tarreau
2023-02-07 2:09 ` [PATCH 2/3] nolibc: Add support for LoongArch chris.chenfeiyang
2023-02-07 14:25 ` Arnd Bergmann
2023-02-07 2:09 ` [PATCH 3/3] selftests/nolibc: " chris.chenfeiyang
2023-02-08 3:54 ` Willy Tarreau
2023-02-08 4:34 ` Paul E. McKenney
2023-02-08 6:39 ` Feiyang Chen
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=17740a63-624f-47da-a701-dd218f95f9da@app.fastmail.com \
--to=arnd@arndb.de \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=chris.chenfeiyang@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®