From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Merck Hung <merckhung@gmail.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: arm: qcom: Add Microsoft Windows Dev Kit 2023
Date: Sun, 27 Oct 2024 21:20:29 +0100 [thread overview]
Message-ID: <ddec1bfa-e97f-42e8-a649-4d04326f250f@kernel.org> (raw)
In-Reply-To: <jcv5ywftxggskbcyzbjmgiacb7kii7zmioenf7jfrqafke7zks@ge4vfzxmxap6>
On 27/10/2024 21:19, Krzysztof Kozlowski wrote:
> On Sun, Oct 27, 2024 at 02:02:16PM +0100, Jens Glathe wrote:
>> Add compatible values for the Microsoft Windows Dev Kit (WDK2023)
>> with its codename "blackrock". The Dev kit is a small desktop box
>> based on the mainboard of the Surface pro 9 5G, intended for
>> developers to test/build arm64-based Windows software.
>> Link: https://learn.microsoft.com/en-us/windows/arm/dev-kit/
>>
>> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
>> ---
>> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> ---
>
> <form letter>
> This is an automated instruction, just in case, because many review tags
> are being ignored. If you know the process, you can skip it (please do
> not feel offended by me posting it here - no bad intentions intended).
> If you do not know the process, here is a short explanation:
>
> Please add Acked-by/Reviewed-by/Tested-by tags when posting new
> versions, under or above your Signed-off-by tag. Tag is "received", when
> provided in a message replied to you on the mailing list. Tools like b4
> can help here. However, there's no need to repost patches *only* to add
> the tags. The upstream maintainer will do that for tags received on the
> version they apply.
>
> https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
> </form letter>
Wrong template. Should be this one:
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-27 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 13:02 [PATCH v4 0/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for Windows Dev Kit 2023 Jens Glathe
2024-10-27 13:02 ` Jens Glathe via B4 Relay
2024-10-27 13:02 ` [PATCH v4 1/3] dt-bindings: arm: qcom: Add Microsoft " Jens Glathe
2024-10-27 13:02 ` Jens Glathe via B4 Relay
2024-10-27 20:19 ` Krzysztof Kozlowski
2024-10-27 20:20 ` Krzysztof Kozlowski [this message]
2024-10-27 13:02 ` [PATCH v4 2/3] firmware: qcom: scm: Allow QSEECOM for " Jens Glathe
2024-10-27 13:02 ` Jens Glathe via B4 Relay
2024-10-27 13:02 ` [PATCH v4 3/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for WDK2023 Jens Glathe
2024-10-27 13:02 ` Jens Glathe via B4 Relay
2024-10-29 20:18 ` Bjorn Andersson
2024-10-29 12:44 ` [PATCH v4 0/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for Windows Dev Kit 2023 Rob Herring (Arm)
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=ddec1bfa-e97f-42e8-a649-4d04326f250f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=merckhung@gmail.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.