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:   Sun, 4 Sep 2016 11:05:44 +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 Sun, Sep 4, 2016 at 2:15 AM, Kevin Hilman <khilman@...libre.com> wrote:
> On Fri, Sep 2, 2016 at 10:33 PM, Jassi Brar <jassisinghbrar@...il.com> wrote:
>> 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 ;)
>
> That's fine with me too.  I offered tot take int just in case you had
> already sent pull requests for this cycle, and also since I'll take
> the DT changes through arm-soc.
>
This revision came after rc2, so it wasn't included. I will queue
patch-1 & 2 for next release, and you the patch-3.

Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ