linux-kernel - Re: linux-next: stats (Was: Linux 4.11-rc1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 6 Mar 2017 20:10:13 +0100
From:   David Sterba <dsterba@...e.cz>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: stats (Was: Linux 4.11-rc1)

Hi,

On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote:
> >  - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.

> Top ten first word of commit summary:
...
>      61 btrfs

I can comment on the btrfs part. We have lots of cleanups for 4.11 and
good part of all the patches are changing function parameters, one per
patch. Therefore the overall counts are high.

The first batch has been in for-next since mid Jan, and the second one
was added right after to the beginning of the merge window (20170221).
All series merged had appeared on the mailinglist a few days before 4.10
release but had to be updated due to some fixes regarding whitespace and
over-80-char lines.

So strictly speaking the patches did come late, but there was very low
risk of breakage. Getting all the queued cleanups out is a relief as
they tend to cause merge conflicts with pending patchsets.