From: Kevin Hilman <khilman@baylibre.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list\:ARM\/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB
Date: Tue, 06 Sep 2016 10:56:18 -0700 [thread overview]
Message-ID: <7hpoogzzct.fsf@baylibre.com> (raw)
In-Reply-To: <CABb+yY10d1+73wjAZCM6PqSXiVC05ZWehK+ugb7rMh8yOh9wNg@mail.gmail.com> (Jassi Brar's message of "Sun, 4 Sep 2016 11:05:44 +0530")
Jassi Brar <jassisinghbrar@gmail.com> writes:
> On Sun, Sep 4, 2016 at 2:15 AM, Kevin Hilman <khilman@baylibre.com> wrote:
>> On Fri, Sep 2, 2016 at 10:33 PM, Jassi Brar <jassisinghbrar@gmail.com> wrote:
>>> On Sat, Sep 3, 2016 at 5:04 AM, Kevin Hilman <khilman@baylibre.com> wrote:
>>>> Hi Jassi,
>>>>
>>>> Neil Armstrong <narmstrong@baylibre.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.
OK, sounds good. Thanks,
Kevin
prev parent reply other threads:[~2016-09-06 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 10:10 [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB Neil Armstrong
2016-08-18 10:10 ` [PATCH v2 1/3] mailbox: Add Platform Message-Handling-Unit variant driver Neil Armstrong
2016-08-18 10:10 ` [PATCH v2 2/3] dt-bindings: mailbox: Add Amlogic Meson MHU Bindings Neil Armstrong
2016-08-18 10:10 ` [PATCH v2 3/3] ARM64: dts: meson-gxbb: Add Meson MHU Node Neil Armstrong
2016-09-07 20:08 ` Kevin Hilman
2016-09-02 23:34 ` [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB Kevin Hilman
2016-09-03 5:33 ` Jassi Brar
2016-09-03 20:45 ` Kevin Hilman
2016-09-04 5:35 ` Jassi Brar
2016-09-06 17:56 ` Kevin Hilman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hpoogzzct.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox