From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Pekka Enberg" <penberg@cs.helsinki.fi>,
"Christoph Lameter" <cl@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Joel Becker" <Joel.Becker@oracle.com>,
"\"Frédéric Weisbecker\"" <fweisbec@gmail.com>,
"Len Brown" <lenb@kernel.org>, "Avi Kivity" <avi@qumranet.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Alasdair G Kergon" <agk@redhat.com>,
"Anton Vorontsov" <avorontsov@ru.mvista.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
"Boaz Harrosh" <bharrosh@panasas.com>,
"Jon Masters" <jonathan@jonmasters.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: Main things left in linux-next
Date: Wed, 24 Jun 2009 09:48:01 +0200 [thread overview]
Message-ID: <20090624074801.GH31415@kernel.dk> (raw)
In-Reply-To: <20090624172735.9b500674.sfr@canb.auug.org.au>
On Wed, Jun 24 2009, Stephen Rothwell wrote:
> Hi All,
>
> $ git diff --shortstat -M stable..HEAD^
> 587 files changed, 27313 insertions(+), 12317 deletions(-)
>
> We seem to be going backwards :-( Yesterday's was:
> 556 files changed, 27596 insertions(+), 7123 deletions(-)
>
> $ git diff --dirstat -M stable..HEAD^
> 4.9% Documentation/powerpc/dts-bindings/
> 5.1% Documentation/powerpc/
> 3.0% Documentation/vm/
> 3.9% arch/sparc/
> 3.9% arch/x86/kvm/
> 4.4% arch/x86/
> 6.9% drivers/md/
> 4.7% drivers/misc/
> 9.8% drivers/staging/et131x/
> 4.3% drivers/staging/
> 6.6% drivers/usb/otg/
> 14.5% drivers/
> 5.5% include/linux/
> 12.6% mm/
>
> The main obvious things left are:
>
> SLQB from the slab tree
> an m68k update
> an ocfs2 update
> the reiserfs kill-the-bkl effort
> an acpi update
> a kvm update
> some more cpumask work from the rr tree
> the writeback changes form the block tree
> a device-mapper update
> a battery tree update
> a leds tree update
> osdblk from the osd tree
> the new hwlat tree
> devtmpfs from the driver-core tree (hmmm?)
>
> Please do not shoot the messenger. :-)
The writeback changes will be sitting there until .32 :-)
--
Jens Axboe
next prev parent reply other threads:[~2009-06-24 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 6:46 linux-next: Tree for June 24 Stephen Rothwell
2009-06-24 7:27 ` Main things left in linux-next Stephen Rothwell
2009-06-24 7:40 ` Pekka Enberg
2009-06-24 7:46 ` Stephen Rothwell
2009-06-24 7:43 ` Jeff Garzik
2009-06-24 7:49 ` Stephen Rothwell
2009-06-24 7:52 ` Jeff Garzik
2009-06-24 7:48 ` Jens Axboe [this message]
2009-06-24 7:52 ` Stephen Rothwell
2009-06-24 8:10 ` Richard Purdie
2009-06-24 12:52 ` Greg KH
2009-06-24 16:35 ` Frederic Weisbecker
2009-06-24 15:34 ` linux-next: Tree for June 24 (kvm/trace) Randy Dunlap
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=20090624074801.GH31415@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Joel.Becker@oracle.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=avorontsov@ru.mvista.com \
--cc=bharrosh@panasas.com \
--cc=cl@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=jonathan@jonmasters.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rpurdie@rpsys.net \
--cc=rusty@rustcorp.com.au \
--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).