All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
	"Eric W. Biederman" <ebiederm@aristanetworks.com>,
	Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] sysfs: Fixup broken chown tracking
Date: Tue, 9 Mar 2010 12:53:03 -0700	[thread overview]
Message-ID: <20100309195303.GH29129@obsidianresearch.com> (raw)
In-Reply-To: <1268163988.29493.1970.camel@moss-terrapins.epoch.ncsc.mil>

On Tue, Mar 09, 2010 at 02:46:28PM -0500, David P. Quigley wrote:
> On Tue, 2010-03-09 at 11:42 -0800, Greg KH wrote:
> > On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> > > It looks like your patch is already in the tree as commit
> > > 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> > > Eric fixed it up. I thought it was very odd that you posted this 5
> > > minutes ago and it was already upstream.
> > 
> > Yeah, this has already been resolved, did that patch not solve the issue
> > for you?
> 
> I don't see how it couldn't have. The patch he submitted which he says
> fixes the problem is the exact same patch that Eric submitted back in
> Feb. Its possible that he is using a version of 2.6.33-rc8 that is based
> off of a commit before the patch was merged since 2.6.33-rc8 was tagged
> on Feb 12th and your commit date in the repo is Feb 16th.

Yes, that is correct, I was only looking up to 2.6.33-rc8, I didn't
think to check Linus's head branch, my mistake. It looks to me like
the changeset you pointed to was put in Linus's tree after that tag,
so it is fixed, just not in any tagged kernel.

Thanks for looking at this,
Jason

  reply	other threads:[~2010-03-09 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 19:11 [PATCH] sysfs: Fixup broken chown tracking Jason Gunthorpe
2010-03-09 19:36 ` David P. Quigley
2010-03-09 19:42   ` Greg KH
2010-03-09 19:46     ` David P. Quigley
2010-03-09 19:53       ` Jason Gunthorpe [this message]
2010-03-09 20:03         ` Greg KH
2010-03-09 20:13           ` Jason Gunthorpe

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=20100309195303.GH29129@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=ebiederm@aristanetworks.com \
    --cc=gregkh@suse.de \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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.