* Re: Linux 4.0-rc1 out..
2015-02-23 5:15 ` Linux 4.0-rc1 out Stephen Rothwell
@ 2015-02-23 8:22 ` Sedat Dilek
2015-02-23 23:14 ` Olof Johansson
2015-02-24 19:40 ` Steven Rostedt
2 siblings, 0 replies; 4+ messages in thread
From: Sedat Dilek @ 2015-02-23 8:22 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Linus Torvalds, Linux Kernel Mailing List, linux-next,
Thorsten Leemhuis
On Mon, Feb 23, 2015 at 6:15 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> As usual, the executive friendly graph is at
> http://neuling.org/linux-next-size.html :-)
>
> I haven't done these for a while, so I haven't included a previous
> release for comparison.
>
> (No merge commits counted, next-20150209 was the last linux-next before
> the merge window opened.)
>
> Commits in v4.0-rc1 (relative to v3.19): 8950
> Commits in next-20140804: 8279
[ CC Thorsten Leemhuis ]
Hi Stephen,
thank you for a statistical overview.
It should be interesting and document the Linux-next development.
Especially what came in from last -next release (release before
v4.0-rc1) into v4.0-rc1 - as you write this was next-20150209.
Is that a typo next-20*14*0804?
How did you generate your statistcs (number of commits, top-ten, etc.)?
Thorsten is doing a fantastic job by explaining what is going on in
the Linux-kernel development in his "Kernel-Log" [1] article series
(German). On the last page he describes how he extracted the "numbers"
(please see [2]).
May have a look at it?
Personally, I don't like any of Linus' -rc1 release announcement (but
I read them).
What are the pearls - what is "worth mentioning" - what new stuff is
worth testing (scripts/diffconfig last-stable-config
latest-rc1-config)?
As someone interested in Linux-kernel I expect to get these
informations more "user-friendly".
( IMO, It is irresponsible that user walk through all commits or
merge-commits. )
As a conclusion:
I am interested in such statistics and thank you for this email.
Thanks.
Regards,
- Sedat -
[1] http://www.heise.de/open/kernel-log-3007.html
[2] http://www.heise.de/open/artikel/Die-Neuerungen-von-Linux-3-19-2541595.html?artikelseite=3
> Commits with the same SHA1: 7492
> Commits with the same patch_id: 452 (1)
> Commits with the same subject line: 70 (1)
>
> (1) not counting those in the lines above.
>
> So commits in -rc1 that were in next-20150209: 8014 89.5%
>
> Some breakdown of the list of extra commits (relative to next-20150209)
> in -rc1:
>
> Top ten first word of commit summary:
>
> 103 mips
> 79 staging
> 37 drm
> 32 lguest
> 25 ib
> 22 arm
> 19 rdma
> 19 input
> 19 alsa
> 18 sunrpc
>
> Top ten authors:
>
> 51 rusty@rustcorp.com.au
> 50 markos.chandras@imgtec.com
> 25 trond.myklebust@primarydata.com
> 21 leonid.yegoshin@imgtec.com
> 19 hch@lst.de
> 17 richard.alpe@ericsson.com
> 16 abbotti@mev.co.uk
> 15 zyan@redhat.com
> 15 arnd@arndb.de
> 14 dhowells@redhat.com
>
> Top ten commiters:
>
> 81 gregkh@linuxfoundation.org
> 75 davem@davemloft.net
> 64 markos.chandras@imgtec.com
> 59 rusty@rustcorp.com.au
> 47 torvalds@linux-foundation.org
> 43 roland@purestorage.com
> 38 ralf@linux-mips.org
> 31 trond.myklebust@primarydata.com
> 26 mingo@kernel.org
> 26 idryomov@gmail.com
>
> There are also 265 commits in next-20150209 that didn't make it into
> v4.0-rc1.
>
> Top ten first word of commit summary:
>
> 25 rcu
> 24 arm
> 20 selftests
> 19 mm
> 11 arm-soc
> 6 documentation
> 5 tracing
> 5 staging
> 5 libceph
> 5 ceph
>
> Top ten authors:
>
> 36 akpm@linux-foundation.org
> 34 paulmck@linux.vnet.ibm.com
> 20 shuahkh@osg.samsung.com
> 11 olof@lixom.net
> 9 minchan@kernel.org
> 7 rostedt@goodmis.org
> 6 zyan@redhat.com
> 6 behanw@converseincode.com
> 5 tapaswenipathak@gmail.com
> 4 namjae.jeon@samsung.com
>
> Some of Andrew's patches are fixes for other patches in his tree (and
> have been merged into those).
>
> Top ten commiters:
>
> 102 sfr@canb.auug.org.au
> 35 paulmck@linux.vnet.ibm.com
> 21 shuahkh@osg.samsung.com
> 11 olof@lixom.net
> 10 idryomov@redhat.com
> 9 kgene@kernel.org
> 7 rostedt@goodmis.org
> 7 behanw@converseincode.com
> 7 arnd@arndb.de
> 4 treding@nvidia.com
>
> Those commits by me are from the quilt series (mainly Andrew's mmotm
> tree).
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Linux 4.0-rc1 out..
2015-02-23 5:15 ` Linux 4.0-rc1 out Stephen Rothwell
2015-02-23 8:22 ` Sedat Dilek
@ 2015-02-23 23:14 ` Olof Johansson
2015-02-24 19:40 ` Steven Rostedt
2 siblings, 0 replies; 4+ messages in thread
From: Olof Johansson @ 2015-02-23 23:14 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Linus Torvalds, Linux Kernel Mailing List,
linux-next@vger.kernel.org
Hi,
On Sun, Feb 22, 2015 at 9:15 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> There are also 265 commits in next-20150209 that didn't make it into
> v4.0-rc1.
>
> Top ten first word of commit summary:
>
> 25 rcu
> 24 arm
> 20 selftests
> 19 mm
> 11 arm-soc
> 6 documentation
> 5 tracing
> 5 staging
> 5 libceph
> 5 ceph
>
> Top ten authors:
>
> 36 akpm@linux-foundation.org
> 34 paulmck@linux.vnet.ibm.com
> 20 shuahkh@osg.samsung.com
> 11 olof@lixom.net
This is expected. We keep a next-only index file of what merges we've
done in arch/arm/arm-soc-for-next-contents.txt which accounts for
these commits.
-Olof
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Linux 4.0-rc1 out..
2015-02-23 5:15 ` Linux 4.0-rc1 out Stephen Rothwell
2015-02-23 8:22 ` Sedat Dilek
2015-02-23 23:14 ` Olof Johansson
@ 2015-02-24 19:40 ` Steven Rostedt
2 siblings, 0 replies; 4+ messages in thread
From: Steven Rostedt @ 2015-02-24 19:40 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Linus Torvalds, Linux Kernel Mailing List, linux-next
On Mon, Feb 23, 2015 at 04:15:41PM +1100, Stephen Rothwell wrote:
>
> There are also 265 commits in next-20150209 that didn't make it into
> v4.0-rc1.
>
> Top ten first word of commit summary:
>
> 25 rcu
> 24 arm
> 20 selftests
> 19 mm
> 11 arm-soc
> 6 documentation
> 5 tracing
Yep, that was my tracefs code. It's all ready to go mainline, but then
I did some stress testing on perf, and found that perf hard coded the
mount id into itself, and ignored traceevents if they were not in the
debugfs system (even if the path was the same!). I sent patches to fix
this but because those patches didn't make it into the release, I decide
to not push this knowing it will cause issues with perf.
Thus, tracefs needs to wait till perf is updated before I push it out.
-- Steve
> 5 staging
> 5 libceph
> 5 ceph
>
^ permalink raw reply [flat|nested] 4+ messages in thread