From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.34-rc1
Date: Mon, 8 Mar 2010 12:33:05 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003081204510.3669@localhost.localdomain> (raw)
It's out there now. I still have a few trees I already got pull requests
for, and that I want to look over a bit more (ceph, gdb tree etc), and
it's possible that I've just overlooked some other pull request.
So if you feel like you sent me a pull request bit might have been
over-looked, please point that out to me, but in general the merge window
is over. And as promised, if you left your pull request to the last day of
a two-week window, you're now going to have to wait for the 2.6.35 window.
As usual, there's tons of changes, with about 50% of the changes being
under drivers/. With an additional 5% in sound/, which has its own
subdirectory, and 10% being firmware/, we're looking at about two thirds
being driver-related.
Of the remaining, about half is arch updqates (mainly arm, mips, ppc, sh
and x86), and half is "rest". Which includes things like a new filesystem
(logfs - as mentioned, there's another one pending too, so we might have
two new ones in 2.6.34).
All in all, about 850 developers involved so far (there migth be a few
dups there, I didn't check too closely), 6500+ files changed, 400,000+
lines added, ~175,000 lines deleted. Too much to really summarize, in
other words.
The thing that bit me, and might bite a few others, is that if you're
using Nouveau, you'll have to install new libdrm/nouveau_drv versions.
Other than that, if something doesn't work, please holler!
Linus
next reply other threads:[~2010-03-08 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 20:33 Linus Torvalds [this message]
2010-03-08 22:06 ` Linux 2.6.34-rc1 Jiri Slaby
2010-03-13 21:56 ` Writable limits (was Re: Linux 2.6.34-rc1) Jiri Kosina
2010-03-23 13:59 ` Pavel Machek
2010-03-09 2:14 ` Linux 2.6.34-rc1 Mike Frysinger
2010-03-09 16:28 ` Jan Kara
2010-03-09 17:13 ` Randy Dunlap
2010-03-11 15:08 ` Please pull UDF updates for 2.6.34-rc1 Jan Kara
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=alpine.LFD.2.00.1003081204510.3669@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--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).