From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Marc Zyngier" <maz@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: "Marijn Suijten" <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH v7 0/2] Resolve MPM register space situation
Date: Sat, 09 Dec 2023 17:08:05 +0000 [thread overview]
Message-ID: <63e4c6098fdf5b7995dab74b415d55d32f757b5c@linux.dev> (raw)
In-Reply-To: <1c99bb49-51e9-458e-acef-a0615dca95ce@linaro.org>
December 9, 2023 at 9:00 AM, "Konrad Dybcio" <konrad.dybcio@linaro.org> wrote:
> > Signed-off-by on the cover letter is completely meaningless.
>
> Yes, I realize that. Blame b4.
It's not -- some subsystems use cover letters as merge commits.
-K
prev parent reply other threads:[~2023-12-09 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:52 [PATCH v7 0/2] Resolve MPM register space situation Konrad Dybcio
2023-11-27 15:52 ` [PATCH v7 1/2] dt-bindings: interrupt-controller: mpm: Pass MSG RAM slice through phandle Konrad Dybcio
2023-11-27 15:52 ` [PATCH v7 2/2] irqchip: irq-qcom-mpm: Support passing a slice of SRAM as reg space Konrad Dybcio
2023-12-08 14:37 ` Thomas Gleixner
2023-12-09 14:23 ` Konrad Dybcio
2023-12-08 14:33 ` [PATCH v7 0/2] Resolve MPM register space situation Thomas Gleixner
2023-12-09 14:00 ` Konrad Dybcio
2023-12-09 17:08 ` Konstantin Ryabitsev [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=63e4c6098fdf5b7995dab74b415d55d32f757b5c@linux.dev \
--to=konstantin.ryabitsev@linux.dev \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
/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).