public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	tiffany.lin@mediatek.com, andrew-ct.chen@mediatek.com,
	linux-mediatek@lists.infradead.org,
	Eugen Hristev <eugen.hristev@collabora.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	bin.liu@mediatek.com
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH v3 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count
Date: Tue, 30 Jan 2024 09:35:00 +0100	[thread overview]
Message-ID: <2a918b33-eb95-40d2-9a96-8799e86c66bc@collabora.com> (raw)
In-Reply-To: <bf79f44f-5fa7-4341-8deb-605503d33c7c@gmail.com>

Il 29/01/24 16:46, Matthias Brugger ha scritto:
> 
> 
> On 29/01/2024 11:41, AngeloGioacchino Del Regno wrote:
>>
>> On Sat, 27 Jan 2024 10:42:57 +0200, Eugen Hristev wrote:
>>> MT8186 has 4 iommus in the list, to cope with this situation, adjust
>>> the maxItems to 4 (instead of previous 2).
>>> Add also minItems as 2 to keep compatibility with current devices.
>>>
>>>
>>
>> Applied to v6.4-next/dts64, thanks!
>>
>> [1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count
>>        commit: b824b32dd5e98221cbe2e8bcccc6fb4134e35fc1
> 
> Hm, not sure why you took this one, as DT-Bindings normally go through the 
> subsystem maintainer trees. Otherwise merge conflicts can occur. Just saying.
> 

That was done so that we don't get devicetree validation issues on our branch;
eventually, there were no driver changes to support that binding change, and
it's there just to validate commit 2/2.

Of course the media maintainers do know about this so there will be no merge
conflict - but yes next time I'll let them pick these instead, it's probably
easier for everyone, besides simply being the proper thing to do.

Angelo

> Matthias
> 
> 
>> [2/2] arm64: dts: mediatek: mt8186: Add jpgenc node
>>        commit: 4c5b46fbf52d52b0f392f0fc3913560bad438e49
>>
>> Best regards,


      reply	other threads:[~2024-01-30  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  8:42 [PATCH v3 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count Eugen Hristev
2024-01-27  8:42 ` [PATCH v3 2/2] arm64: dts: mediatek: mt8186: Add jpgenc node Eugen Hristev
2024-01-29 10:32   ` AngeloGioacchino Del Regno
2024-01-29 10:41 ` [PATCH v3 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count AngeloGioacchino Del Regno
2024-01-29 10:47   ` AngeloGioacchino Del Regno
2024-01-30  3:24     ` Chen-Yu Tsai
2024-01-30  8:39       ` AngeloGioacchino Del Regno
2024-01-29 15:46   ` Matthias Brugger
2024-01-30  8:35     ` AngeloGioacchino Del Regno [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=2a918b33-eb95-40d2-9a96-8799e86c66bc@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=andrew-ct.chen@mediatek.com \
    --cc=bin.liu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eugen.hristev@collabora.com \
    --cc=kernel@collabora.com \
    --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=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tiffany.lin@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