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:   Sun, 29 Jan 2017 20:30:34 +0000
From:   Chris Packham <>
To:     Stephen Boyd <>,
        Gregory CLEMENT <>
CC:     Linus Walleij <>,
        "" <>,
        Rob Herring <>,
        Mark Rutland <>,
        Michael Turquette <>,
        Jason Cooper <>,
        Andrew Lunn <>,
        Sebastian Hesselbarth <>,
        Geert Uytterhoeven <>,
        Chris Brand <>,
        Florian Fainelli <>,
        "Arnd Bergmann" <>,
        Thierry Reding <>,
        Sudeep Holla <>,
        Juri Lelli <>,
        Thomas Petazzoni <>,
        Laxman Dewangan <>,
        Kalyan Kinthada <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>
Subject: Re: [PATCHv5 0/5] Support for Marvell switches with integrated CPUs

On 28/01/17 07:47, Stephen Boyd wrote:
> On 01/27, Gregory CLEMENT wrote:
>> Hi all,
>>  On ven., janv. 27 2017, Chris Packham <> wrote:
>>> The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with
>>> integrated CPUs. They CPU block is common within these product lines and
>>> (as far as I can tell/have been told) is based on the Armada XP. There
>>> are a few differences due to the fact they have to squeeze the CPU into
>>> the same package as the switch.
>>> I've rebased this series against linux-pinctrl/devel to get access to
>>> mvebu_mmio_mpp_ctrl. Everything else still applies cleanly to
>>> v4.10.0-rc5.
>> Just to let you know that I plan to apply the 3 arm patch once Chris
>> will have sent the new series with the minor fixes I asked on patch 3.
>> I already applied them in the for-next branch to benefit of some build
>> test coverage.
>> Stephen,
>> you gave your Acked-by on the first patch, but don't you plan to apply
>> it on the clk branch?
> It must have not been clear if I should apply it, hence the ack.
> I'll apply it now.

Sorry my bad. I need all 5 together in one place to actually test the 

I wasn't sure whether the series should go through mvebu with Acks from 
clk and pinctrl or if things should go to the separate maintainers and 
come together when they hit the main linux repo. Up until the latest 
pinctrl change either approach would have worked.

Powered by blists - more mailing lists