linux-kernel - Re: linux-next: Tree for May 17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 17 May 2019 14:56:34 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     ktkhai@...tuozzo.com
CC:     Stephen Rothwell <sfr@...b.auug.org.au>, atish.patra@....com,
        linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject:     Re: linux-next: Tree for May 17

On Fri, 17 May 2019 02:43:08 PDT (-0700), ktkhai@...tuozzo.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.

Ya, sorry about that.  It should have been fixed as of last night -- I must
have just done something stupid.