From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matt Turner <mattst88@gmail•com>
Cc: "Eric W. Biederman" <ebiederm@xmission•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Michael Cree <mcree@orcon•net.nz>
Subject: Re: linux-next: manual merge of the namespace tree with Linus' tree
Date: Mon, 16 May 2011 14:44:05 +1000 [thread overview]
Message-ID: <20110516144405.50ea1b77.sfr@canb.auug.org.au> (raw)
In-Reply-To: <BANLkTinvz_jCQhdZP46FY89e8amqvdqaeg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
Hi Matt,
On Mon, 16 May 2011 00:00:15 -0400 Matt Turner <mattst88@gmail•com> wrote:
>
> I don't know what the best way to avoid this is. Sometimes (and
> _sometimes_ is the problem) new syscalls are added through another
> tree. Other times, they're added to only x86 and amd64 or something
> and leave us to find out later.
>
> So, should all syscall additions go through the respective arch trees,
> or should syscall additions make sure to include all architectures?
Any and all of the above should be fine. Mostly, the "only add x86"
model is followed and the other arches catch up later.
Conflicts like these are easy to handle and Linus does not mind fixing
them up as they occur, so for really simple syscalls, adding them to all
architectures should be fine.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-05-16 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 3:47 linux-next: manual merge of the namespace tree with Linus' tree Stephen Rothwell
2011-05-16 4:00 ` Matt Turner
2011-05-16 4:44 ` Stephen Rothwell [this message]
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=20110516144405.50ea1b77.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ebiederm@xmission$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mattst88@gmail$(echo .)com \
--cc=mcree@orcon$(echo .)net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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