linux-kernel - Re: [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB

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]

Message-ID: <CABb+yY2Cq5KaCCvoJ5afsLfqc5NEoPMkaaYk9GjFO8=N80eVBA@mail.gmail.com>
Date:   Sat, 3 Sep 2016 11:03:54 +0530
From:   Jassi Brar <jassisinghbrar@...il.com>
To:     Kevin Hilman <khilman@...libre.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB

On Sat, Sep 3, 2016 at 5:04 AM, Kevin Hilman <khilman@...libre.com> wrote:
> Hi Jassi,
>
> Neil Armstrong <narmstrong@...libre.com> writes:
>
>> In order to support Mailbox links for the Amlogic GXBB SoC, add a generic
>> platform MHU driver based on arm_mhu.c.
>>
>> This patchset follows a RFC thread along the GXBB SCPI support at :
>> http://lkml.kernel.org/r/1466503374-28841-1-git-send-email-narmstrong@baylibre.com
>> And specific MHU discussions at :
>> http://lkml.kernel.org/r/CABb+yY3HqJG2+GMWCWF9PomxobrwWGZ=TZe5NvXPcHMDdLhkcQ@mail.gmail.com
>>
>> Changes since v1 at http://lkml.kernel.org/r/1470732737-18391-1-git-send-email-narmstrong@baylibre.com :
>>  - Fix irq to signed to detect platform_get_irq() failures
>>  - Introduced back the secure channel
>>  - Fixed indexes
>
> How is this version looking to you?
>
> With your review/ack on the driver, I'd be happy to take it via the
> amlogic tree as there shouldn't be any conflicts with your tree.
>
I am ok with the driver, but I don't understand how it helps going via
amlogic tree. I would like to send a pull request every release ;)

cheers.