From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Gole, Dhruva" <d-gole@ti.com>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-spi@vger.kernel.org, "Mark Brown" <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spi-mem: Fix typo (of -> or)
Date: Fri, 28 Oct 2022 11:55:23 +0200 [thread overview]
Message-ID: <Y1unCzyjQ1ZzgU/S@probook> (raw)
In-Reply-To: <0f5235b8-9f35-6f7c-37b4-8094e476fbd4@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Fri, Oct 28, 2022 at 12:00:23PM +0530, Gole, Dhruva wrote:
> Hi Jonathan,
>
> On 10/8/2022 8:44 PM, Jonathan Neuschäfer wrote:
> > In this instance, "or" makes more sense than "of", so I guess that "or"
> > was intended and "of" was a typo.
>
> Using "I guess" is generally discouraged in commit messages. Please read up
> the documentation
It is truthful though: I did not write the original comment, and my
change is based on my interpretation of the comment.
> on submitting patches:
>
> > Describe your changes in imperative mood, e.g. “make xyzzy do frotz”
> instead of “[This patch] makes xyzzy do frotz” or “[I] changed xyzzy to do
> frotz”, as if you are giving orders to the codebase to change its behaviour.
The imperative-mood description is already in the commit title
(or subject line). I am not making a functional change to the code, so
"fix a typo" is really all that is to be said in imperative mood, the
rest is an explanation of why I think this makes sense.
>
> link: https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
Best regards,
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-28 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 15:14 [PATCH] spi: spi-mem: Fix typo (of -> or) Jonathan Neuschäfer
2022-10-28 6:30 ` Gole, Dhruva
2022-10-28 9:55 ` Jonathan Neuschäfer [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=Y1unCzyjQ1ZzgU/S@probook \
--to=j.neuschaefer@gmx.net \
--cc=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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