From: Johan Hovold <johan@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp-lenovo-thinkpad: correct pin drive-strength
Date: Thu, 13 Apr 2023 11:11:07 +0200 [thread overview]
Message-ID: <ZDfHK2pfHtq5hgfD@hovoldconsulting.com> (raw)
In-Reply-To: <a84b11c7-c49d-6859-cdd7-16b4d37489df@linaro.org>
On Thu, Apr 13, 2023 at 10:53:07AM +0200, Krzysztof Kozlowski wrote:
> On 12/04/2023 09:19, Johan Hovold wrote:
> > The general suggestion is still to check 'git log --oneline' for the
> > files in question and use what appears to be the (recent) common prefix.
>
> I do it for subsystems, but I am not going to do it per file. Sorry, I
> am sending way too many of them to keep also customizing them per each
> file.
Perhaps you should start grouping your patch bombs of identical changes
rather than send them per file if this is such a burden.
Either way, that is no excuse when changing a single file.
> If you wanted x13s prefix, then you would name the file like that.
> If you named file differently, then apparently that's how you want it to
> look.
No, that is not what we want. The git log tells you what we expect. And
the x13s prefix is there, you just randomly decided to drop it.
Johan
prev parent reply other threads:[~2023-04-13 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:07 [PATCH] arm64: dts: qcom: sc8280xp-lenovo-thinkpad: correct pin drive-strength Krzysztof Kozlowski
2023-04-07 18:57 ` Bjorn Andersson
2023-04-11 14:23 ` Johan Hovold
2023-04-11 16:58 ` Krzysztof Kozlowski
2023-04-12 6:49 ` Johan Hovold
2023-04-12 7:03 ` Krzysztof Kozlowski
2023-04-12 7:19 ` Johan Hovold
2023-04-12 7:22 ` Konrad Dybcio
2023-04-13 8:53 ` Krzysztof Kozlowski
2023-04-13 8:53 ` Krzysztof Kozlowski
2023-04-13 9:11 ` Johan Hovold [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=ZDfHK2pfHtq5hgfD@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@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=robh+dt@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