From: 王洪亮 <wanghongliang@loongson.cn>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: add loongarch64 port
Date: Sat, 2 Apr 2022 17:53:41 +0800 [thread overview]
Message-ID: <ea4d06ce-6f89-54a0-ae2c-4c0995d4edcd@loongson.cn> (raw)
In-Reply-To: <20220402072138.GI7074@brightrain.aerifal.cx>
在 2022/4/2 下午3:21, Rich Felker 写道:
> On Sat, Apr 02, 2022 at 02:19:44PM +0800, 王洪亮 wrote:
>> Hi, Arnd
>>
>> I found it has not been removed from system call list in kernel yet.
>> I wonder if I could keep consistent with the current status of the kernel
>> for the time being,and modify as the kernel changes.
> As I understand it, no -- musl targets the permanent kernel syscall
> API/ABI for the arch. So if the legacy stat syscall is not going to be
> part of the interface that's approved upstream in the kernel for this
> arch, musl can't be using it.
>
> Am I correct in understanding that the syscall & struct stat that are
> "there now" are part of a proposed port that's not yet upstream, and
> that upstream maintainers are asking for them to be removed as part of
> accepting the port?
>
Hi, Rich
yes, but it has not been removed from kernel port yet,the Author hopes
to keep it,so I consider modify it when the issue comes to a conclusion.
Hongliang Wang
>> 在 2022/4/1 下午3:48, Arnd Bergmann 写道:
>>> On Fri, Apr 1, 2022 at 9:40 AM 王洪亮 <wanghongliang@loongson.cn> wrote:
>>>> 在 2022/3/31 下午4:14, Arnd Bergmann 写道:
>>>>
>>>> In kernel port, loongarch64 use the generic struct stat.
>>>>
>>>> loongarch64 define struct stat and kstat in musl is consistent with
>>>>
>>>> generic stat in kernel.
>>> My point was that I asked for these to be removed in
>>>
>>> https://lore.kernel.org/lkml/CAK8P3a2kroHVN3fTabuFVMz08SXytz-SC8X11BxxszsUCksJ4g@mail.gmail.com/
>>>
>>> With __NR_newfstatat and __NR_fstat gone from the system
>>> call list, there is no 'struct stat' that is exposed by the kernel.
>>>
>>> Arnd
next prev parent reply other threads:[~2022-04-02 9:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 6:20 王洪亮
2022-03-31 8:14 ` Arnd Bergmann
2022-04-01 7:40 ` 王洪亮
2022-04-01 7:48 ` Arnd Bergmann
2022-04-02 6:19 ` 王洪亮
2022-04-02 7:21 ` Rich Felker
2022-04-02 9:53 ` 王洪亮 [this message]
2022-04-27 1:58 ` 王洪亮
2022-04-27 2:13 ` Rich Felker
2022-03-31 18:47 ` Rich Felker
2022-04-02 7:59 ` 王洪亮
2022-04-06 2:08 ` 王洪亮
2022-04-06 16:00 ` Markus Wichmann
2022-04-08 2:21 ` 王洪亮
2022-04-08 6:46 ` Arnd Bergmann
2022-04-09 3:54 ` 王洪亮
2022-04-09 11:06 ` Arnd Bergmann
2022-04-09 13:19 ` Rich Felker
2022-04-09 13:30 ` Rich Felker
2022-04-10 10:30 ` Arnd Bergmann
2022-04-10 15:26 ` Rich Felker
2022-04-11 8:03 ` Arnd Bergmann
2022-04-11 12:11 ` Rich Felker
2022-04-11 13:01 ` Arnd Bergmann
2022-04-12 1:11 ` 王洪亮
2022-04-13 1:16 ` 王洪亮
2022-04-13 7:26 ` Christian Brauner
2022-04-13 8:26 ` Arnd Bergmann
2022-04-13 9:04 ` Christian Brauner
2022-04-13 13:25 ` Arnd Bergmann
2022-04-13 14:09 ` Rich Felker
2022-04-14 9:36 ` Christian Brauner
2022-04-20 9:09 ` 王洪亮
2022-04-20 13:33 ` Christian Brauner
2022-04-20 13:54 ` Rich Felker
2022-04-21 6:54 ` 王洪亮
2022-04-14 9:36 ` Christian Brauner
2022-04-13 7:19 ` Christian Brauner
2022-04-13 14:06 ` Rich Felker
2022-04-11 3:40 ` 王洪亮
-- strict thread matches above, loose matches on Subject: below --
2022-03-22 3:52 [musl] " 王洪亮
2022-03-29 8:12 ` [musl] " 王洪亮
2022-03-29 8:26 ` Arnd Bergmann
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=ea4d06ce-6f89-54a0-ae2c-4c0995d4edcd@loongson.cn \
--to=wanghongliang@loongson.cn \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).