From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Mark Brown <broonie@kernel.org>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
martin.botka@somainline.org,
angelogioacchino.delregno@somainline.org,
marijn.suijten@somainline.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] qcom: spmi-regulator: Add support for ULT LV_P50 and ULT P300
Date: Mon, 1 Mar 2021 15:27:05 +0100 [thread overview]
Message-ID: <eff6b950-45fa-9a1e-8596-1646916f25f7@somainline.org> (raw)
In-Reply-To: <20210301142359.GA20302@sirena.org.uk>
On 01.03.2021 15:23, Mark Brown wrote:
> On Thu, Feb 25, 2021 at 10:35:13PM +0100, Konrad Dybcio wrote:
>> From: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
>>
>> The ULT LV_P50 shares the same configuration as the other ULT LV_Pxxx
>> and the ULT P300 shares the same as the other ULT Pxxx.
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
Yeah, sorry for that.. We've had these changes for a veery long time and it now the fact that the commit title was sub-optimal went under our radar.. Hopefully won't happen again!
Konrad
next prev parent reply other threads:[~2021-03-01 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:35 [PATCH] qcom: spmi-regulator: Add support for ULT LV_P50 and ULT P300 Konrad Dybcio
2021-03-01 14:23 ` Mark Brown
2021-03-01 14:27 ` Konrad Dybcio [this message]
2021-03-01 23:37 ` Mark Brown
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=eff6b950-45fa-9a1e-8596-1646916f25f7@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=phone-devel@vger.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 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).