All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: stats (Was: Linux 4.11-rc1)
Date: Mon, 6 Mar 2017 20:10:13 +0100	[thread overview]
Message-ID: <20170306191013.GQ4662@twin.jikos.cz> (raw)
In-Reply-To: <20170306105200.58e8143b@canb.auug.org.au>

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.

      reply	other threads:[~2017-03-06 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 21:41 Linux 4.11-rc1 Linus Torvalds
2017-03-05 23:52 ` linux-next: stats (Was: Linux 4.11-rc1) Stephen Rothwell
2017-03-06 19:10   ` David Sterba [this message]

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=20170306191013.GQ4662@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.