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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 May 2020 03:42:17 +0300
From:   Serge Semin <>
To:     Thomas Bogendoerfer <>
CC:     Serge Semin <>,
        Alexey Malahov <>,
        Maxim Kaurkin <>,
        Pavel Parkhomenko <>,
        Ramil Zaripov <>,
        Ekaterina Skachko <>,
        Vadim Vlasov <>,
        Alexey Kolotnikov <>,
        Paul Burton <>,
        Ralf Baechle <>,
        Rob Herring <>,
        Frank Rowand <>,
        Tony Lindgren <>,
        Arnd Bergmann <>, Olof Johansson <>,
        Greg Kroah-Hartman <>,
        Jiri Slaby <>, <>,
        <>, <>
Subject: Re: [PATCH v3 00/14] mips: Prepare MIPS-arch code for Baikal-T1 SoC

On Thu, May 21, 2020 at 03:34:29AM +0300, Serge Semin wrote:


> This patchset is rebased and tested on the mainline Linux kernel 5.7-rc4:
> base-commit: 0e698dfa2822 ("Linux 5.7-rc4")
> tag: v5.7-rc4

Please note that this patchset is based on the Linux 5.7-rc4 tree (it most likely
will get cleanly applied on rc6 as well), while mips-next is still at rc1. Due
to that the patchset fails to be applied on mips-next. I think it would be
better first to merge the last Linux tree into the mips-next, then try to merge
this patchset in. Should you have any problem after that, please let me know.
I'll resend the patchset being rebased on top of the new mips-next tree.


Powered by blists - more mailing lists