From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs: Fixup broken chown tracking
Date: Tue, 9 Mar 2010 13:13:58 -0700 [thread overview]
Message-ID: <20100309201358.GG30462@obsidianresearch.com> (raw)
In-Reply-To: <20100309200319.GA13609@suse.de>
On Tue, Mar 09, 2010 at 12:03:19PM -0800, Greg KH wrote:
> > 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.
>
> 2.6.33 is tagged, as is 2.6.34-rc1, so it should be showing up on your
> end by now :)
s/tagged kernel/tagged kernel in my git pull/
Network troubles today :|
git.kernel.org[0: 149.20.20.136]: errno=Connection timed out
Thanks,
Jason
prev parent reply other threads:[~2010-03-09 20:14 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
2010-03-09 20:03 ` Greg KH
2010-03-09 20:13 ` Jason Gunthorpe [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=20100309201358.GG30462@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.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 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).