From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845: Use the Low Power Island CX/MX for SLPI
Date: Tue, 02 Jan 2024 09:07:20 +0100 [thread overview]
Message-ID: <875y0c5fbb.fsf@baylibre.com> (raw)
In-Reply-To: <f1dd06a5-d5f6-40bf-b4c9-5b073b329b04@linaro.org>
Hi Konrad,
On Wed, Dec 27, 2023 at 01:53, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
> On 22.12.2023 19:43, Konstantin Ryabitsev wrote:
>> On Wed, Dec 20, 2023 at 03:16:00PM +0100, Konrad Dybcio wrote:
>>> On 20.12.2023 15:15, Konrad Dybcio wrote:
>>>> The SLPI is powered by the Low Power Island power rails. Fix the incorrect
>>>> assignment.
>>>>
>>>> Fixes: 74588aada59a ("arm64: dts: qcom: sdm845: add SLPI remoteproc")
>>>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>>>> ---
>>> b4 seems to not have included my "only compile-tested" comment
>>
>> Can you let me know your expected behaviour vs. what you ended up seeing?
> Sure!
>
> expected: the "Only compile-tested" bit goes under the striped
> line
>
> actual: The line is ignored. And I think this happens quite
Per my understanding, this is a "feature", not a bug.
What happens on single patches that don't want to have an additional
comment below the --- marker?
> consistently with a single patch with a single line of 'cover
> letter' only, maybe it interprets the series topic, but a
> separate 0/1 message is of course not created.
Can't this be fixed with adding a body in the commit message for 0/1 ?
See below
>
>
>
> Here's the setup:
>
>
> --------------------------------------------
> commit f516d7b26e4aa2e6ac87f7e989de008a99e5b26b (topic/sdm845_slpi_lcxmx)
> Author: Konrad Dybcio <konrad.dybcio@linaro.org>
> Date: Wed Dec 20 15:12:56 2023 +0100
>
> arm64: dts: qcom: sdm845: Use the Low Power Island CX/MX for SLPI
>
> The SLPI is powered by the Low Power Island power rails. Fix the incorrect
> assignment.
>
> Fixes: 74588aada59a ("arm64: dts: qcom: sdm845: add SLPI remoteproc")
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
> commit d8d0c7257dd4cba8ca0f9f8cdfc7ab12adfd3909
> Author: Konrad Dybcio <konrad.dybcio@linaro.org>
> Date: Wed Dec 20 15:14:34 2023 +0100
>
> Only compile-tested # gets ignored
Add another line here: Only compile-tested.
>
> To: Bjorn Andersson <andersson@kernel.org>
> To: Rob Herring <robh+dt@kernel.org>
> To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> To: Conor Dooley <conor+dt@kernel.org>
> To: Dylan Van Assche <me@dylanvanassche.be>
> Cc: Marijn Suijten <marijn.suijten@somainline.org>
> Cc: linux-arm-msm@vger.kernel.org
> Cc: devicetree@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: Caleb Connolly <caleb.connolly@linaro.org>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
> ---
> Changes in v2:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v1: https://lore.kernel.org/r/20231220-topic-sdm845_slpi_lcxmx-v1-1-db7c72ef99ae@linaro.org
>
>
>
> --- b4-submit-tracking ---
> # This section is used internally by b4 prep for tracking purposes.
> {
> "series": {
> "revision": 2,
> "change-id": "20231220-topic-sdm845_slpi_lcxmx-03c4f98a423d",
> "base-branch": null,
> "prefixes": [],
> "history": {
> "v1": [
> "20231220-topic-sdm845_slpi_lcxmx-v1-1-db7c72ef99ae@linaro.org"
> ]
> }
> }
> }
>
> commit 20d857259d7d10cd0d5e8b60608455986167cfad (tag: next-20231220)
>
> --------------------------------------------
>
> Konrad
prev parent reply other threads:[~2024-01-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231220-topic-sdm845_slpi_lcxmx-v1-1-db7c72ef99ae@linaro.org>
[not found] ` <9dc9b23b-6ebb-45b2-a03e-1379a4ceab90@linaro.org>
2023-12-22 18:43 ` [PATCH] arm64: dts: qcom: sdm845: Use the Low Power Island CX/MX for SLPI Konstantin Ryabitsev
2023-12-27 0:53 ` Konrad Dybcio
2024-01-02 8:07 ` Mattijs Korpershoek [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=875y0c5fbb.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=konrad.dybcio@linaro.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.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 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).