From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Steve French <sfrench@us.ibm.com>
Subject: Re: Resolved merge conflicts in next-creds
Date: Tue, 12 Aug 2008 09:36:24 +1000 [thread overview]
Message-ID: <20080812093624.de7d4ad8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LRH.1.10.0808120751001.10017@tundra.namei.org>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Hi James, David,
On Tue, 12 Aug 2008 07:53:40 +1000 (EST) James Morris <jmorris@namei.org> wrote:
>
> We have tried this approach thus far without success, although perhaps now
> the code has been in linux-next and you've come to the same conclusion, we
> could try again.
>
> David, if you want to make a minimal API-only patch set, I'll can stage it
> and push to Linus.
The important thing (and what is different in what I have proposed) is
that what you are asking Linus to take here has zero impact (i.e. you just
add a header file that noone uses and whose contents are clearly noops)
and then it is very obvious that when people start to use it, the changes
really cannot introduce a regression.
Of course, Linus has to be convinced that the long term API change is
sensible as well.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-11 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 23:57 James Morris
2008-08-11 0:16 ` Stephen Rothwell
2008-08-11 5:35 ` Stephen Rothwell
2008-08-11 21:53 ` James Morris
2008-08-11 23:36 ` Stephen Rothwell [this message]
2008-08-12 9:27 ` David Howells
2008-08-12 11:19 ` Stephen Rothwell
2008-08-11 14:51 ` Steven French
2008-08-11 23:39 ` Stephen Rothwell
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=20080812093624.de7d4ad8.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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
all inboxes | Powered by JetHome®