From: lukas walter <lukas.walter@aceart.de>
To: konrad.dybcio@linaro.org
Cc: agross@kernel.org, andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas.walter@aceart.de, phone-devel@vger.kernel.org,
raymondhackley@protonmail.com, robh+dt@kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 2/2] arm64: dts: qcom: msm8939-huawei-kiwi: Add initial device tree
Date: Thu, 05 Oct 2023 16:20:57 +0200 [thread overview]
Message-ID: <284103cfa6bc312ccf12a552dd61d12108fabfbd.camel@aceart.de> (raw)
In-Reply-To: <8e6a41b2-7ad9-4cc6-8f95-93b8c2e4151f@linaro.org>
>> Is this fine?
>> Should I send a V2 with the signoff and reserved-memory changes?
>I don't quite get it, what signoff?
Krzysztof noticed that the Signed-off-by are in the wrong order.
But I was told this alone is not worth a V2.
next prev parent reply other threads:[~2023-10-05 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 13:41 [PATCH 1/2] dt-bindings: arm: qcom: Add Huawei Honor 5X / GR5 (2016) Lukas Walter
2023-09-16 13:41 ` [PATCH 2/2] arm64: dts: qcom: msm8939-huawei-kiwi: Add initial device tree Lukas Walter
2023-09-16 20:39 ` Krzysztof Kozlowski
2023-09-17 13:17 ` lukas walter
2023-09-17 0:22 ` Bryan O'Donoghue
2023-09-17 13:20 ` lukas walter
2023-09-20 14:47 ` Konrad Dybcio
2023-09-25 14:28 ` lukas walter
2023-09-25 14:34 ` Konrad Dybcio
2023-10-05 14:20 ` lukas walter [this message]
2023-09-16 20:38 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Huawei Honor 5X / GR5 (2016) Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 14:30 Lukas Walter
2023-10-21 14:30 ` [PATCH 2/2] arm64: dts: qcom: msm8939-huawei-kiwi: Add initial device tree Lukas Walter
2023-10-21 17:34 ` Konrad Dybcio
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=284103cfa6bc312ccf12a552dd61d12108fabfbd.camel@aceart.de \
--to=lukas.walter@aceart.de \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=raymondhackley@protonmail.com \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.