linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>, Hsin-Yi Wang <hsinyi@chromium.org>,
	Jassi Brar <jaswinder.singh@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	linux-mediatek@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>
Subject: Re: [PATCH v3 2/2] dt-bindings: mediatek: Add optional mediatek, gce-events property
Date: Wed, 12 May 2021 17:55:21 +0200	[thread overview]
Message-ID: <a573e490-44bd-d6a1-d0c0-075b6541f720@gmail.com> (raw)
In-Reply-To: <20210506203124.GA753747@robh.at.kernel.org>

Hi Jassi,

On 06/05/2021 22:31, Rob Herring wrote:
> On Tue, 04 May 2021 13:46:12 +0800, Hsin-Yi Wang wrote:
>> This property is used by gce clients.
>>
>> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
>> ---
>> v2->v3: move definition to Documentation/devicetree/bindings/mailbox/mtk-gce.txt
>> ---
>>  .../devicetree/bindings/mailbox/mtk-gce.txt       | 15 +++++++++++++++
>>  1 file changed, 15 insertions(+)
>>
> 
> Acked-by: Rob Herring <robh@kernel.org>
> 

Will you take this through your branch, or do you prefer me taking it through mine?

Regards,
Matthias

  reply	other threads:[~2021-05-12 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04  5:46 [PATCH v3 1/2] arm64: dts: mt8183: add mediatek,gce-events in mutex Hsin-Yi Wang
2021-05-04  5:46 ` [PATCH v3 2/2] dt-bindings: mediatek: Add optional mediatek,gce-events property Hsin-Yi Wang
2021-05-06 20:31   ` [PATCH v3 2/2] dt-bindings: mediatek: Add optional mediatek, gce-events property Rob Herring
2021-05-12 15:55     ` Matthias Brugger [this message]
2021-05-14  3:24       ` Jassi Brar
2021-07-02 10:33         ` Hsin-Yi Wang

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=a573e490-44bd-d6a1-d0c0-075b6541f720@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=hsinyi@chromium.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).