All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, James Morris <jmorris@namei.org>,
	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 10:27:08 +0100	[thread overview]
Message-ID: <22136.1218533228@redhat.com> (raw)
In-Reply-To: <20080812093624.de7d4ad8.sfr@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> 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.

Actually, you do have to modify XFS too.  It declares current_fsuid(),
current_fsgid() and struct cred within itself.  The first two just require
some simple renames, and the third just requires using my struct cred instead
when it appears.

David

  reply	other threads:[~2008-08-12  9:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 23:57 Resolved merge conflicts in next-creds 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
2008-08-12  9:27         ` David Howells [this message]
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=22136.1218533228@redhat.com \
    --to=dhowells@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.