From: Kirill Tkhai <ktkhai@virtuozzo•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
atish.patra@wdc•com,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for May 17
Date: Fri, 17 May 2019 12:41:30 +0300 [thread overview]
Message-ID: <a119ca58-6771-cc36-fe5a-187ba500010a@virtuozzo.com> (raw)
In-Reply-To: <20190517142152.588edb6e@canb.auug.org.au>
On 17.05.2019 07:21, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.3 material to your linux-next included
> trees/branches until after v5.2-rc1 has been released.
>
> Changes since 20190516:
>
> The kvm tree gained conflicts against Linus' tree.
>
> Non-merge commits (relative to Linus' tree): 1023
> 1119 files changed, 27058 insertions(+), 7629 deletions(-)
Binary file was added:
~/linux-next$ git log --oneline ./modules.builtin.modinfo
4cbb0d07b4d1 RISC-V: Support nr_cpus command line option.
Kirill
next prev parent reply other threads:[~2019-05-17 9:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 4:21 linux-next: Tree for May 17 Stephen Rothwell
2019-05-17 7:33 ` Anders Roxell
2019-05-17 9:41 ` Kirill Tkhai [this message]
2019-05-17 9:43 ` Kirill Tkhai
2019-05-17 9:53 ` Stephen Rothwell
2019-05-17 21:56 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 3:39 Stephen Rothwell
2023-05-17 2:05 Stephen Rothwell
2022-05-17 9:41 Stephen Rothwell
2018-05-17 7:06 Stephen Rothwell
2018-05-17 18:03 ` Naresh Kamboju
2018-05-22 14:18 ` Mark Brown
2018-05-23 23:07 ` Mark Brown
2017-05-17 4:17 Stephen Rothwell
2016-05-17 5:04 Stephen Rothwell
2016-05-23 8:13 ` Xiong Zhou
2016-05-23 8:37 ` Stephen Rothwell
2016-05-24 4:52 ` Xiong Zhou
2013-05-17 4:21 Stephen Rothwell
2012-05-17 7:46 Stephen Rothwell
2011-05-17 4:27 Stephen Rothwell
2010-05-17 6:35 Stephen Rothwell
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=a119ca58-6771-cc36-fe5a-187ba500010a@virtuozzo.com \
--to=ktkhai@virtuozzo$(echo .)com \
--cc=atish.patra@wdc$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox