From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of arch/arm in linux-next
Date: Thu, 14 Apr 2011 10:44:47 +0100 [thread overview]
Message-ID: <20110414094447.GA1611@n2100.arm.linux.org.uk> (raw)
This morning, I looked at linux-next to find out how arch/arm is doing
for the next merge window.
$ git diff -C --cumulative v2.6.39-rc1... arch
19.7% arch/arm/mach-imx/
19.2% arch/arm/mach-mx3/
3.4% arch/arm/mach-mxc91231/
18.1% arch/arm/mach-ux500/
74.1% arch/arm/
3.2% arch/m68k/
4.0% arch/mips/lantiq/
6.9% arch/mips/
3.1% arch/x86/kvm/
7.6% arch/x86/
100.0% arch/
$ git diff -C --cumulative v2.6.39-rc1... arch/arm
4.7% arch/arm/mach-imx/
5.9% arch/arm/mach-msm/
6.3% arch/arm/mach-mx3/
8.8% arch/arm/mach-mxc91231/
7.6% arch/arm/mach-ux500/include/mach/
46.1% arch/arm/mach-ux500/
3.6% arch/arm/mach-zynq/
5.9% arch/arm/plat-mxc/include/mach/
7.3% arch/arm/plat-mxc/
100.0% arch/arm/
$ git diff -C --shortstat v2.6.39-rc1... arch/arm
450 files changed, 11973 insertions(+), 5736 deletions(-)
Note that with --cumulative, the %age given includes all child directories
(so the 74% for arch/arm includes everything below it).
So, almost 75% of changes in arch are down to arch/arm. For arch/arm,
there's 6k new lines introduced - so there's a significant amount of new
work there.
Folk may want to consider that we're three weeks from Linus' rant, and
there's little sign of the situation changing. It looks to me from
these statistics that it's business as usual.
Please take a moment to consider how Linus will react to this at the
next merge window.
next reply other threads:[~2011-04-14 9:44 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 9:44 Russell King - ARM Linux [this message]
2011-04-14 11:08 ` Status of arch/arm in linux-next Tony Lindgren
2011-04-14 12:02 ` Russell King - ARM Linux
2011-04-14 12:31 ` Tony Lindgren
2011-04-14 14:20 ` Mark Brown
2011-04-14 14:26 ` Tony Lindgren
2011-04-14 14:31 ` Russell King - ARM Linux
2011-04-14 18:32 ` Mark Brown
2011-04-15 15:12 ` Grant Likely
2011-04-15 15:56 ` Russell King - ARM Linux
2011-04-15 16:10 ` Grant Likely
2011-04-16 8:28 ` Russell King - ARM Linux
2011-04-16 16:57 ` Mark Brown
2011-04-18 8:10 ` Tony Lindgren
2011-04-18 13:57 ` Mark Brown
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 15:58 ` Mark Brown
2011-04-18 17:18 ` Russell King - ARM Linux
2011-04-18 20:23 ` Mark Brown
2011-04-18 21:40 ` Thomas Gleixner
2011-04-18 23:55 ` Mark Brown
2011-04-14 14:07 ` Mark Brown
2011-04-15 2:59 ` Nico Erfurth
2011-04-15 8:21 ` Nicolas Ferre
2011-04-15 13:13 ` Nico Erfurth
2011-04-15 1:16 ` Linus Walleij
2011-04-15 6:26 ` Tony Lindgren
2011-04-19 14:16 ` Arnd Bergmann
2011-04-19 14:50 ` Mark Brown
2011-04-19 14:55 ` Arnd Bergmann
2011-04-19 15:04 ` Mark Brown
2011-04-19 15:14 ` Linus Walleij
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:05 ` Mark Brown
2011-04-21 20:14 ` Dave Jones
2011-04-21 21:02 ` Nicolas Pitre
2011-04-22 7:17 ` Tony Lindgren
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 18:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-30 0:05 ` Nicolas Pitre
2011-05-01 23:02 ` Jamie Lokier
2011-04-19 16:27 ` Dave Jones
2011-04-19 17:12 ` Arnd Bergmann
2011-04-20 6:36 ` Linus Walleij
2011-04-21 7:32 ` Linus Walleij
2011-04-21 8:25 ` Arnd Bergmann
2011-04-22 7:56 ` Linus Walleij
2011-04-22 11:46 ` Linus Walleij
2011-05-02 13:49 ` Samuel Ortiz
2011-05-02 19:21 ` Linus Walleij
2011-04-20 7:33 ` Tony Lindgren
2011-04-20 7:43 ` Arnd Bergmann
2011-04-15 14:30 ` Martin Guy
2011-04-15 15:50 ` Russell King - ARM Linux
2011-04-18 15:17 ` Alexey Zaytsev
2011-04-18 16:23 ` Linus Torvalds
2011-04-18 21:54 ` Alexey Zaytsev
2011-04-19 15:02 ` Linus Torvalds
2011-04-19 15:20 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110414094447.GA1611@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).