From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Michal Marek <mmarek@suse.cz>
Subject: Re: Linux 2.6.35-rc6
Date: Fri, 23 Jul 2010 05:22:13 -0700 [thread overview]
Message-ID: <20100723122213.GA689@kroah.com> (raw)
In-Reply-To: <20100723112142.f698394e.sfr@canb.auug.org.au>
On Fri, Jul 23, 2010 at 11:21:42AM +1000, Stephen Rothwell wrote:
> Hi Linus,
>
> On Thu, 22 Jul 2010 12:26:13 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> I actually hope/think that this is going to be the last -rc. Things
> > have been pretty quiet, and while this -rc has more commits than -rc5
> > had, it's not by a large amount, nor does it look scary to me. So
> > there doesn't seem to be any point in dragging out the release any
> > more, unless we find something new that calls for it.
>
> I have no idea how important this stuff is, but I still have the
> following in linux-next that are (in theory) destined for v2.6.35:
<snip>
Yes, there are a few minor USB patches in my tree (minor bugfixes and
new device ids) that I wanted to send to you, but no need to hold up a
.35 release.
We're still working on the network namespace sysfs issues, but if that
option is disabled, all works fine. I have 3 tiny patches to work to
resolve that problem in my tree, I can send them to you tonight if you
want.
But even there, nothing that should hold up .35 from release.
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-23 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinJe-oHpgQqnTPQyKUtmKhg2oUJmylkBPALuzGh@mail.gmail.com>
2010-07-23 1:21 ` Linux 2.6.35-rc6 Stephen Rothwell
2010-07-23 12:22 ` Greg KH [this message]
2010-07-23 20:16 ` Rafael J. Wysocki
2010-07-24 8:06 ` Jiri Slaby
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=20100723122213.GA689@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mmarek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).