public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kirill Tkhai <ktkhai@virtuozzo•com>
Cc: atish.patra@wdc•com, palmer@sifive•com,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for May 17
Date: Fri, 17 May 2019 19:53:40 +1000	[thread overview]
Message-ID: <20190517195340.269ba527@canb.auug.org.au> (raw)
In-Reply-To: <07e1a10a-5348-2d2e-fb6a-c9ef837185fe@virtuozzo.com>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

Hi all,

On Fri, 17 May 2019 12:43:08 +0300 Kirill Tkhai <ktkhai@virtuozzo•com> wrote:
>
> On 17.05.2019 12:41, Kirill Tkhai wrote:
> > 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.  
> 
> CC Palmer.

It's been fixed in the risc-v tree since it was included in linux-next
today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-05-17  9:53 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
2019-05-17  9:43   ` Kirill Tkhai
2019-05-17  9:53     ` Stephen Rothwell [this message]
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=20190517195340.269ba527@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=atish.patra@wdc$(echo .)com \
    --cc=ktkhai@virtuozzo$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=palmer@sifive$(echo .)com \
    /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