From: "H. Peter Anvin" <hpa@zytor.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"Theodore Ts'o" <tytso@mit.edu>, Arnd Bergmann <arnd@arndb.de>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Cc: 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>
Subject: Re: [GIT PULL] ext4 changes for 3.15
Date: Wed, 09 Apr 2014 09:55:28 -0700 [thread overview]
Message-ID: <53457B80.1080307@zytor.com> (raw)
In-Reply-To: <CAMuHMdW8xkBFJ5-E04rVhDk+CSubHut+kx3P6cYCn0dMhQdb-Q@mail.gmail.com>
On 04/09/2014 09:40 AM, Geert Uytterhoeven wrote:
> On Tue, Apr 8, 2014 at 3:47 PM, Theodore Ts'o <tytso@mit.edu> wrote:
>> On Mon, Apr 07, 2014 at 10:25:30PM +0200, Geert Uytterhoeven wrote:
>>>> maintainers would have no idea that a new syscall has been added.
>>>
>>> If i386 has the new syscall, scripts/checksyscalls.sh will catch it and
>>> inform us about it during our next kernel build.
>>>
>>> If you add it to x86_64 only, bad luck for anyone else ;-)
>>
>> Maybe we should change scripts/checksyscalls.sh to check the x86_64
>> list of syscalls, and not i386?
>>
>> It's been a long time since "all the world's an i386" --- these days,
>> it's "all the world's an x86_64". :-)
>
> Let the kbuild people (and their employers) fight over it...
>
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.
-hpa
next prev parent reply other threads:[~2014-04-09 16:56 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 [this message]
2014-04-09 17:48 ` Geert Uytterhoeven
2014-04-09 18:23 ` Theodore Ts'o
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=53457B80.1080307@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--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=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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).