Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Hsin-Yi Wang <hsinyi@chromium.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-media@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	yong.wu@mediatek.com
Subject: Re: [v6 3/3] arm64: dts: mt8183: add jpeg enc node for mt8183
Date: Tue, 1 Mar 2022 08:30:10 +0100	[thread overview]
Message-ID: <d229ad74-b530-af2b-2e01-a60e525186d4@gmail.com> (raw)
In-Reply-To: <aa54361f-6a8f-a616-640a-b9a098d82cba@collabora.com>



On 17/02/2022 10:41, AngeloGioacchino Del Regno wrote:
> Il 06/12/21 14:04, Hsin-Yi Wang ha scritto:
>> From: Maoguang Meng <maoguang.meng@mediatek.com>
>>
>> Add jpeg encoder device tree node.
>>
>> Signed-off-by: Maoguang Meng <maoguang.meng@mediatek.com>
>> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> 
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> 

Applied, thanks!

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

  reply	other threads:[~2022-03-01  8:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 13:04 [v6 1/3] dt-bindings: mediatek: convert mtk jpeg decoder/encoder to yaml Hsin-Yi Wang
2021-12-06 13:04 ` [v6 2/3] dt-bindings: mediatek: Add mediatek, mt8183-jpgenc compatible Hsin-Yi Wang
2022-02-17  9:41   ` AngeloGioacchino Del Regno
2021-12-06 13:04 ` [v6 3/3] arm64: dts: mt8183: add jpeg enc node for mt8183 Hsin-Yi Wang
2022-02-17  9:41   ` AngeloGioacchino Del Regno
2022-03-01  7:30     ` Matthias Brugger [this message]
2022-02-16 17:13 ` [v6 1/3] dt-bindings: mediatek: convert mtk jpeg decoder/encoder to yaml Benjamin Gaignard
2022-02-17  9:41 ` AngeloGioacchino Del Regno

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=d229ad74-b530-af2b-2e01-a60e525186d4@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsinyi@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=yong.wu@mediatek.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