All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sebastian Reichel <sre@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: stats (Was: Linux 4.12-rc1)
Date: Tue, 16 May 2017 07:32:09 +1000	[thread overview]
Message-ID: <20170516073200.147ed148@canb.auug.org.au> (raw)
In-Reply-To: <20170515145108.mpk2uhiz7o6mtbpy@earth>

Hi Sebastian,

On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel <sre@kernel.org> wrote:
>
> On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote:
> > There are also 288 commits in next-20170502 that didn't make it into
> > v4.12-rc1.
> > 
> > [...]
> >
> > Top ten commiters:
> > 
> >      66 sfr@canb.auug.org.au
> >      47 paulmck@linux.vnet.ibm.com
> >      34 tglx@linutronix.de
> >      23 linux@roeck-us.net
> >      14 alexandre.belloni@free-electrons.com
> >      11 peda@axentia.se
> >       9 quwenruo@cn.fujitsu.com
> >       8 olof@lixom.net
> >       7 sre@kernel.org
> >       5 mathieu.poirier@linaro.org  
> 
> Did you compile the list today? I started adding content for 4.13
> after Linus tagged v4.12-rc1 and my power-supply for-next branch
> curently has exactly 7 patches.

As I said above these are commits that were in linux-next on May 2nd
but were not in v4.12-rc1:

99484df028dd power: supply: bq27xxx: Add power_supply_battery_info support
ac8eb82d2fed power: supply: bq27xxx: Add chip data memory read/write support
a66c51d4fe5a power: supply: bq27xxx: Add bulk transfer bus methods
7192174d20dc dt-bindings: power: supply: bq27xxx: Add monitored-battery documentation
fb38342a5ae6 power: supply: core: add power_supply_battery_info and API
bbdc4f09fe12 devicetree: property-units: Add uWh and uAh units
ecc931a585b3 dt-bindings: power: supply: add simple-battery DT binding

There can be various reasons that they didn't make it in and, in fact,
these are not in yesterday's linux-next either.
-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-05-15 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-40777@linuxfoundation>
2017-05-13 20:57 ` Linux 4.12-rc1 Linus Torvalds
2017-05-14 17:59   ` Linux 4.12-rc1 (file locations) Randy Dunlap
2017-05-15 15:42     ` Linus Torvalds
2017-05-15 15:42       ` [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] " Linus Torvalds via RT
2017-05-15 18:34         ` François Valenduc
2017-05-15 18:34           ` François Valenduc via RT
     [not found]           ` <rt-4.4.0-31767-1494873296-832.40777-6-0@linuxfoundation>
2017-05-15 18:42             ` [Kernel.org Helpdesk " Konstantin Ryabitsev via RT
2017-05-24 18:34               ` Christian Kujau
2017-05-24 18:42                 ` Christian Kujau via RT
     [not found]                 ` <rt-4.4.0-12250-1495651374-7.40777-6-0@linuxfoundation>
2017-05-24 20:14                   ` Konstantin Ryabitsev via RT
     [not found]       ` <rt-4.4.0-31807-1494862968-1551.40777-6-0@linuxfoundation>
2017-05-16 21:22         ` Konstantin Ryabitsev via RT
2017-05-15 18:45     ` Konstantin Ryabitsev via RT
2017-05-15 13:15   ` linux-next: stats (Was: Linux 4.12-rc1) Stephen Rothwell
2017-05-15 14:51     ` Sebastian Reichel
2017-05-15 21:32       ` Stephen Rothwell [this message]
2017-05-20 16:33         ` Sebastian Reichel

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=20170516073200.147ed148@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sre@kernel.org \
    --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.