From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754391AbdCFTMe (ORCPT ); Mon, 6 Mar 2017 14:12:34 -0500 Received: from mx2.suse.de ([195.135.220.15]:54643 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932152AbdCFTM1 (ORCPT ); Mon, 6 Mar 2017 14:12:27 -0500 Date: Mon, 6 Mar 2017 20:10:13 +0100 From: David Sterba To: Stephen Rothwell Cc: Linus Torvalds , Linux Kernel Mailing List Subject: Re: linux-next: stats (Was: Linux 4.11-rc1) Message-ID: <20170306191013.GQ4662@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Stephen Rothwell , Linus Torvalds , Linux Kernel Mailing List References: <20170306105200.58e8143b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170306105200.58e8143b@canb.auug.org.au> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.