From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Dongjin Kim <tobetter@gmail.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 1/4] dt-bindings: arm: rockchip: Correct vendor for Hardkernel ODROID-M1
Date: Tue, 27 Aug 2024 08:50:27 +0200 [thread overview]
Message-ID: <bf6145b6-8dd7-40e8-8b33-7eacd2c20a37@kernel.org> (raw)
In-Reply-To: <66ccebe1.c80a0220.22579e.e8daSMTPIN_ADDED_BROKEN@mx.google.com>
On 26/08/2024 22:55, Jonas Karlman wrote:
> The vendor prefix for Hardkernel ODROID-M1 is incorrectly listed as
> rockchip. Use the proper hardkernel vendor prefix for this board.
>
> Fixes: 19cc53eb2ce6 ("dt-bindings: rockchip: Add Hardkernel ODROID-M1 board")
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
Your messages are broken somehow. Broken message id, rewritten by google
but I cannot grab the thread neither by original nor by "fixed" message-id:
b4 ... 66ccebe1.c80a0220.22579e.e8daSMTPIN_ADDED_BROKEN@mx.google.com
Grabbing thread from
lore.kernel.org/all/66ccebe1.c80a0220.22579e.e8daSMTPIN_ADDED_BROKEN@mx.google.com/t.mbox.gz
That message-id is not known.
b4 ... '20240826205538.1066103-1-jonas@kwiboo.se'
Grabbing thread from
lore.kernel.org/all/20240826205538.1066103-1-jonas@kwiboo.se/t.mbox.gz
CRITICAL: '20240826205538.1066103-1-jonas@kwiboo.se
Anyway, this was sent:
https://lore.kernel.org/all/20240116192605.GA274661-robh@kernel.org/
it is technically ABI break, but likely without practical impact.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-27 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 20:55 [PATCH 0/4] arm64: dts: rockchip: Add Hardkernel ODROID-M1S Jonas Karlman
2024-08-26 20:55 ` [PATCH 1/4] dt-bindings: arm: rockchip: Correct vendor for Hardkernel ODROID-M1 Jonas Karlman
2024-08-26 21:14 ` Aurelien Jarno
2024-08-26 20:55 ` [PATCH 2/4] arm64: dts: rockchip: Correct vendor prefix " Jonas Karlman
2024-08-26 21:14 ` Aurelien Jarno
2024-08-26 20:55 ` [PATCH 3/4] dt-bindings: arm: rockchip: Add Hardkernel ODROID-M1S Jonas Karlman
2024-08-26 20:55 ` [PATCH 4/4] arm64: dts: " Jonas Karlman
[not found] ` <66ccebe1.c80a0220.22579e.e8daSMTPIN_ADDED_BROKEN@mx.google.com>
2024-08-27 6:50 ` Krzysztof Kozlowski [this message]
2024-08-27 11:17 ` [PATCH 1/4] dt-bindings: arm: rockchip: Correct vendor for Hardkernel ODROID-M1 Jonas Karlman
[not found] ` <66ccebeb.d40a0220.356790.58caSMTPIN_ADDED_BROKEN@mx.google.com>
2024-08-27 6:52 ` [PATCH 3/4] dt-bindings: arm: rockchip: Add Hardkernel ODROID-M1S Krzysztof Kozlowski
2024-08-27 11:29 ` Jonas Karlman
2024-08-27 11:44 ` Heiko Stuebner
2024-08-27 13:01 ` Jonas Karlman
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=bf6145b6-8dd7-40e8-8b33-7eacd2c20a37@kernel.org \
--to=krzk@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tobetter@gmail.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;
as well as URLs for NNTP newsgroup(s).