From: Theodore Ts'o <tytso@mit.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Arnd Bergmann <arnd@arndb.de>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>, Jan Kara <jack@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [GIT PULL] ext4 changes for 3.15
Date: Wed, 9 Apr 2014 14:23:24 -0400 [thread overview]
Message-ID: <20140409182324.GA778@thunk.org> (raw)
In-Reply-To: <CAMuHMdU9ZcCzRWk2NWfdx54Uox=C=MaR5t8sD2icUpE_xtr8cA@mail.gmail.com>
On Wed, Apr 09, 2014 at 07:48:32PM +0200, Geert Uytterhoeven wrote:
> >
> > I'm missing context here, but as an x86 maintainer I have no intention
> > of allowing system calls that aren't x86-specific to be added to x86-64
> > only.
>
> commit 520c8b16505236fc82daa352e6c5e73cd9870cff
> Author: Miklos Szeredi <mszeredi@suse.cz>
> Date: Tue Apr 1 17:08:42 2014 +0200
>
> vfs: add renameat2 syscall
>
> It was added to arch/x86/syscalls/syscall_64.tbl only.
To be fair, part of the problem is that we don't have good
documentation about best practices in what people should do if adding
new system calls. (i.e., creating a man page and pulling in Michael
Kerrisk, adding tests, wiring up both x86_64 and i386, sending mail to
linux-arch, the scripts/checksyscalls.sh script, etc.)
I'll confess to being ignorant about the checksyscalls.sh script, and
while I had known about the existence of the linux-arch list, I had
forgotten about it, so if I had tried to add a new system call, it's
likely I would have missed at one or more of these steps.
- Ted
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
next prev parent reply other threads:[~2014-04-09 18:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 19:15 [GIT PULL] ext4 changes for 3.15 Theodore Ts'o
2014-04-03 19:39 ` Linus Torvalds
2014-04-04 3:53 ` Theodore Ts'o
2014-04-04 13:44 ` Jan Kara
2014-04-04 17:16 ` Miklos Szeredi
2014-04-04 20:23 ` Theodore Ts'o
2014-04-08 10:47 ` Dave Chinner
2014-04-04 23:43 ` Theodore Ts'o
2014-04-07 13:15 ` Miklos Szeredi
2014-04-07 14:07 ` Theodore Ts'o
2014-04-07 20:25 ` Geert Uytterhoeven
2014-04-08 11:25 ` Heiko Carstens
2014-04-08 16:25 ` Linus Torvalds
2014-04-08 13:47 ` Theodore Ts'o
2014-04-09 16:40 ` Geert Uytterhoeven
2014-04-09 16:55 ` H. Peter Anvin
2014-04-09 17:48 ` Geert Uytterhoeven
2014-04-09 18:23 ` Theodore Ts'o [this message]
2014-04-09 19:19 ` H. Peter Anvin
2014-06-24 22:03 ` Maciej W. Rozycki
2014-06-24 22:39 ` Thavatchai Makphaibulchoke
2014-06-24 23:25 ` Maciej W. Rozycki
2014-06-25 17:08 ` Linus Torvalds
2014-06-25 22:37 ` Theodore Ts'o
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=20140409182324.GA778@thunk.org \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mtk.manpages@gmail.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).