From: Krzysztof Kozlowski <krzk@kernel.org>
To: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: nvmem: qfprom: Add ipq5210 & ipq9650 compatible
Date: Wed, 3 Jun 2026 16:04:43 +0200 [thread overview]
Message-ID: <d46a7c9c-ef20-434e-a373-c7f519335230@kernel.org> (raw)
In-Reply-To: <aiAQ4lzRoRIzAXT4@hu-varada-blr.qualcomm.com>
On 03/06/2026 13:32, Varadarajan Narayanan wrote:
> On Sat, May 16, 2026 at 11:55:35AM +0200, Krzysztof Kozlowski wrote:
>> On Fri, May 15, 2026 at 02:54:34PM +0530, Varadarajan Narayanan wrote:
>>> Document compatible string for the QFPROM on ipq5210 & ipq9650 platforms.
>>
>> Please wrap commit message according to Linux coding style / submission
>> process (neither too early nor over the limit):
>> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>>
>> This applies to all your patches, not only to this one.
>
> I had incorrectly wrapped to 72 columns instead of 75. Will fix that.
>
> However, in this commit log there is only one line, not sure what to change.
> Am I missing something? Please let me know.
Hm, that was two weeks ago, so I don't know what I had in mind that time
but I imagine it was too long. If you checked and it is fine, then
disregard the comment.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-03 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:24 Varadarajan Narayanan
2026-05-16 9:55 ` Krzysztof Kozlowski
2026-06-03 11:32 ` Varadarajan Narayanan
2026-06-03 14:04 ` Krzysztof Kozlowski [this message]
2026-06-04 4:06 ` Varadarajan Narayanan
2026-06-04 7:25 ` Krzysztof Kozlowski
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=d46a7c9c-ef20-434e-a373-c7f519335230@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=varadarajan.narayanan@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®