From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Reserve syscall number 319
Date: Wed, 03 Sep 2008 07:49:10 +1000 [thread overview]
Message-ID: <1220392150.13010.178.camel@pasglop> (raw)
In-Reply-To: <20080902213044.GA11416@lixom.net>
On Tue, 2008-09-02 at 16:30 -0500, Olof Johansson wrote:
> On Wed, Sep 03, 2008 at 07:06:15AM +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2008-09-02 at 13:06 -0500, Olof Johansson wrote:
> > > On Tue, Sep 02, 2008 at 03:48:45PM +1000, Benjamin Herrenschmidt wrote:
> > > > Some stuff I'm working on that isn't released yet needs
> > > > a syscall number but I can't say what it's for until I
> > > > get permission to release it :-)
> > > >
> > > > In the meantime, it would be nice if a number could be set
> > > > aside so the tools being developped to use that stuff don't
> > > > all need to be updated when things are eventually released.
> > > >
> > > > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > > > ---
> > > >
> > > > I wonder if I'll get hanged for that one :-)
> > >
> > > Yes. Merge your code or live with the pain of things changing
> > > underneath. Period.
> >
> > Pain isn't for me :-) It's for those writing userspace stuff based on
> > my kernel changing all the time :-)
>
> Lame excuse. Merge the code.
man, you know as well as I do I can't do that before the lawyers let
me :-)
Ben.
next prev parent reply other threads:[~2008-09-02 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 5:48 [PATCH] powerpc: Reserve syscall number 319 Benjamin Herrenschmidt
2008-09-02 12:08 ` Josh Boyer
2008-09-02 21:02 ` Benjamin Herrenschmidt
2008-09-02 18:06 ` Olof Johansson
2008-09-02 21:06 ` Benjamin Herrenschmidt
2008-09-02 21:30 ` Olof Johansson
2008-09-02 21:49 ` Benjamin Herrenschmidt [this message]
2008-09-02 22:12 ` Olof Johansson
2008-09-02 22:49 ` Benjamin Herrenschmidt
2008-09-02 23:46 ` Christoph Hellwig
2008-09-03 0:58 ` Benjamin Herrenschmidt
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=1220392150.13010.178.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).