From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Detlev Casanova <detlev.casanova@collabora.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
kernel@collabora.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/3] media: dt-bindings: rockchip,vdec: Correct reg-names order for RK35{76,88}
Date: Tue, 24 Feb 2026 14:18:55 +0100 [thread overview]
Message-ID: <0874bb3d-b38d-4ea3-a5b0-2da2484cc3e5@kernel.org> (raw)
In-Reply-To: <244b22d3be77047163b4e47c4ed33b5b1befb4b4.camel@collabora.com>
On 24/02/2026 14:14, Nicolas Dufresne wrote:
>>>
>>> reg-names:
>>> - items:
>>> + oneOf:
>>> - const: function
>>> - - const: link
>>> - - const: cache
>>> + - items:
>>> + - const: link
>>> + - const: function
>>> + - const: cache
>>
>> No, ABI break without point.
>
> Its not released yet, otherwise both order would need to be allowed.
>
Also, not true.
git describe --contains c6ffb7e1fb90
v6.17-rc1~90^2~3
So clearly released.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Detlev Casanova <detlev.casanova@collabora.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
kernel@collabora.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/3] media: dt-bindings: rockchip,vdec: Correct reg-names order for RK35{76,88}
Date: Tue, 24 Feb 2026 14:18:55 +0100 [thread overview]
Message-ID: <0874bb3d-b38d-4ea3-a5b0-2da2484cc3e5@kernel.org> (raw)
In-Reply-To: <244b22d3be77047163b4e47c4ed33b5b1befb4b4.camel@collabora.com>
On 24/02/2026 14:14, Nicolas Dufresne wrote:
>>>
>>> reg-names:
>>> - items:
>>> + oneOf:
>>> - const: function
>>> - - const: link
>>> - - const: cache
>>> + - items:
>>> + - const: link
>>> + - const: function
>>> + - const: cache
>>
>> No, ABI break without point.
>
> Its not released yet, otherwise both order would need to be allowed.
>
Also, not true.
git describe --contains c6ffb7e1fb90
v6.17-rc1~90^2~3
So clearly released.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-02-24 13:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:49 [PATCH v2 0/3] arm64: dts: rockchip: Fix vdec register blocks order on RK3576/RK3588 Cristian Ciocaltea
2026-02-23 19:49 ` Cristian Ciocaltea
2026-02-23 19:49 ` [PATCH v2 1/3] media: dt-bindings: rockchip,vdec: Correct reg-names order for RK35{76,88} Cristian Ciocaltea
2026-02-23 19:49 ` Cristian Ciocaltea
2026-02-23 23:05 ` Heiko Stübner
2026-02-23 23:05 ` Heiko Stübner
2026-02-24 7:17 ` Krzysztof Kozlowski
2026-02-24 7:17 ` Krzysztof Kozlowski
2026-02-24 13:14 ` Nicolas Dufresne
2026-02-24 13:14 ` Nicolas Dufresne
2026-02-24 13:17 ` Krzysztof Kozlowski
2026-02-24 13:17 ` Krzysztof Kozlowski
2026-02-24 13:18 ` Krzysztof Kozlowski [this message]
2026-02-24 13:18 ` Krzysztof Kozlowski
2026-02-24 13:48 ` Nicolas Dufresne
2026-02-24 13:48 ` Nicolas Dufresne
2026-02-24 13:54 ` Krzysztof Kozlowski
2026-02-24 13:54 ` Krzysztof Kozlowski
2026-02-24 14:07 ` Cristian Ciocaltea
2026-02-24 14:07 ` Cristian Ciocaltea
2026-02-24 14:34 ` Krzysztof Kozlowski
2026-02-24 14:34 ` Krzysztof Kozlowski
2026-02-23 19:49 ` [PATCH v2 2/3] arm64: dts: rockchip: Fix vdec register blocks order on RK3576 Cristian Ciocaltea
2026-02-23 19:49 ` Cristian Ciocaltea
2026-02-24 7:22 ` Krzysztof Kozlowski
2026-02-24 7:22 ` Krzysztof Kozlowski
2026-02-24 13:17 ` Nicolas Dufresne
2026-02-24 13:17 ` Nicolas Dufresne
2026-02-24 13:20 ` Krzysztof Kozlowski
2026-02-24 13:20 ` Krzysztof Kozlowski
2026-02-23 19:49 ` [PATCH v2 3/3] arm64: dts: rockchip: Fix vdec register blocks order on RK3588 Cristian Ciocaltea
2026-02-23 19:49 ` Cristian Ciocaltea
2026-02-24 7:18 ` Krzysztof Kozlowski
2026-02-24 7:18 ` Krzysztof Kozlowski
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=0874bb3d-b38d-4ea3-a5b0-2da2484cc3e5@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil@kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.