linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>, Fabien Parent <fparent@baylibre.com>
Cc: devicetree@vger.kernel.org, sean.wang@mediatek.com,
	linux-kernel@vger.kernel.org, vkoul@kernel.org,
	robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
	dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC
Date: Fri, 27 Nov 2020 09:46:35 +0100	[thread overview]
Message-ID: <4e7974e6-fd47-f1e6-9bf4-bd9762033c2d@gmail.com> (raw)
In-Reply-To: <20201019211634.GA3616126@bogus>

Hi Vinod,

On 19/10/2020 23:16, Rob Herring wrote:
> On Thu, 15 Oct 2020 14:33:14 +0200, Fabien Parent wrote:
>> Add bindings to APDMA for MT8516 SoC. MT8516 is compatible with MT6577.
>>
>> Signed-off-by: Fabien Parent <fparent@baylibre.com>
>> ---
>>   Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt | 1 +
>>   1 file changed, 1 insertion(+)
>>
> 
> Acked-by: Rob Herring <robh@kernel.org>
> 

Will you take this patch through your tree or do you prefer that I take it.

Regards,
Matthias

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      reply	other threads:[~2020-11-27  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 12:33 [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC Fabien Parent
2020-10-15 12:33 ` [PATCH 2/2] arm64: dts: mediatek: mt8516: add support for APDMA Fabien Parent
2020-10-19 10:24 ` [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC Matthias Brugger
2020-10-19 21:16 ` Rob Herring
2020-11-27  8:46   ` Matthias Brugger [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=4e7974e6-fd47-f1e6-9bf4-bd9762033c2d@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fparent@baylibre.com \
    --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 \
    --cc=sean.wang@mediatek.com \
    --cc=vkoul@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).