From: <yunqiang.su@cipunited.com>
To: "'Adhemerval Zanella'" <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Cc: <aurelien@aurel32.net>, <jiaxun.yang@flygoat.com>,
<macro@orcam.me.uk>, <syq@debian.org>
Subject: 回复: [PATCH v2 2/2] MIPS: N64, make xstat as wrapper of generic fstatat
Date: Mon, 22 Mar 2021 10:23:33 +0800 [thread overview]
Message-ID: <000d01d71ec2$5e4492c0$1acdb840$@cipunited.com> (raw)
In-Reply-To: <a3aca740-5d98-0775-f4b7-dd8efcecb577@linaro.org>
>
> On 18/03/2021 22:18, YunQiang Su wrote:
> > fxstatat as wrapper of fstatat
> > fxstatat64 as wrapper of fstatat64
> >
> > fxstat, lxstat, xstat as wrapper of fxstatat fxstat64, lxstat64,
> > xstat64 as wrapper of fxstatat64
>
> Sorry I am still unconvinced that compat symbols worth the maintainability
> burden and these implementations takes a complete opposite turn of the
> recent consolidation and simplification we are doing on the glibc codebase.
>
> If user does want a y2106 ready binary it should build against a newer glibc, I
> just send a fix [1] that handle on both the non-LFS and the LFS symbol.
>
Thank you. The major problem has been resolved. And anyway, Y2106 is far enough.
> [1] https://patchwork.sourceware.org/project/glibc/list/?series=1878
next prev parent reply other threads:[~2021-03-22 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 1:18 [PATCH v2 1/2] fstatat64: use statx on kernel using uint32 for time YunQiang Su
2021-03-19 1:18 ` [PATCH v2 2/2] MIPS: N64, make xstat as wrapper of generic fstatat YunQiang Su
2021-03-19 10:07 ` Andreas Schwab
2021-03-19 18:42 ` Adhemerval Zanella
2021-03-22 2:23 ` yunqiang.su [this message]
2021-03-19 18:38 ` [PATCH v2 1/2] fstatat64: use statx on kernel using uint32 for time Adhemerval Zanella
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='000d01d71ec2$5e4492c0$1acdb840$@cipunited.com' \
--to=yunqiang.su@cipunited.com \
--cc=adhemerval.zanella@linaro.org \
--cc=aurelien@aurel32.net \
--cc=jiaxun.yang@flygoat.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=syq@debian.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).