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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 22 May 2020 12:34:43 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Jisheng Zhang <Jisheng.Zhang@...aptics.com>
Cc:     Geert Uytterhoeven <geert+renesas@...der.be>,
        SoC Team <soc@...nel.org>, Kevin Hilman <khilman@...nel.org>,
        Olof Johansson <olof@...om.net>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH v2 06/15] ARM: berlin: Drop unneeded select of HAVE_SMP

On Fri, May 22, 2020 at 12:13 PM Jisheng Zhang
<Jisheng.Zhang@...aptics.com> wrote:
>
> Hi Arnd, Kevin, Olof,
>
> On Tue,  5 May 2020 17:07:13 +0200 Geert Uytterhoeven wrote:
>
> >
> >
> > Support for Marvell Berlin SoCs depends on ARCH_MULTI_V7.
> > As the latter selects HAVE_SMP, there is no need for MACH_BERLIN_BG2 to
> > select HAVE_SMP.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> > Cc: Jisheng Zhang <Jisheng.Zhang@...aptics.com>
> > Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
> > Acked-by: Arnd Bergmann <arnd@...db.de>
>
> The patch looks good to me. I want to know what will be the mainline
> path of this series. SoC maintainers take it then send A PR to arm-soc?
> Or each SoC maintainers ack it, arm-soc will take the whole series?
> If later, then
>
> Acked-by: Jisheng Zhang <Jisheng.Zhang@...aptics.com>
>
>
> This is the first time I see a series touch different SoC platforms.

I have already merged it. The normal way we do this is that platform
maintainers can choose to merge individual patches when they
are happy with them on the early review, or provide an Ack for
them to get merged as a branch.

I picked up v2 of the series as there seemed to be a sufficient
number of Acks and everyone that commented had agreed
in principle.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ