From: "Arnd Bergmann" <arnd@arndb.de>
To: "Sohil Mehta" <sohil.mehta@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] syscalls: Remove file path comments from headers
Date: Fri, 23 Jun 2023 10:06:51 +0200 [thread overview]
Message-ID: <0344615b-5148-4641-a99c-ef75a387b261@app.fastmail.com> (raw)
In-Reply-To: <038984b4-9e95-bc4b-e763-95bf24426f07@intel.com>
On Thu, Jun 22, 2023, at 22:17, Sohil Mehta wrote:
> On 6/22/2023 8:10 AM, Arnd Bergmann wrote:
>> Applied to the asm-generic tree, thanks!
>>
>
> Great, thanks for the quick response.
>
> While going through the comments, I was wondering if we have a
> definition of what constitutes a deprecated syscall vs an obsolete one?
>
> For deprecated we have some information saying:
>> /*
>> * Deprecated system calls which are still defined in
>> * include/uapi/asm-generic/unistd.h and wanted by >= 1 arch
>> */
>
> But, I couldn't find anything for obsolete system calls.
I don't think we've ever defined the two terms properly,
I would assume they are used interchangeably here. If we wanted
a definition, 'obsolete' could mean syscalls that are no longer
used by current software while 'deprecated' are those that
are still called by glibc and others on the architectures that
provide them but are emulated through modern variants on other
architectures. Without any documentation on the topic, or a
definite list, other interpretations are equally possible.
Arnd
next prev parent reply other threads:[~2023-06-23 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 18:31 [PATCH] syscalls: Fix file path names in the header comments Sohil Mehta
2023-06-16 20:11 ` Arnd Bergmann
2023-06-16 20:54 ` Sohil Mehta
2023-06-21 22:36 ` [PATCH] syscalls: Remove file path comments from headers Sohil Mehta
2023-06-22 15:10 ` Arnd Bergmann
2023-06-22 20:17 ` Sohil Mehta
2023-06-23 8:06 ` Arnd Bergmann [this message]
2023-06-23 12:25 ` Christian Brauner
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=0344615b-5148-4641-a99c-ef75a387b261@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@intel.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).