From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
Leonardo Araujo <leonardo.aa88@gmail.com>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] Staging: r8188eu: core: 'associcated' may be misspelled - perhaps 'associated'?
Date: Tue, 8 Feb 2022 13:54:33 +0300 [thread overview]
Message-ID: <20220208105433.GI1951@kadam> (raw)
In-Reply-To: <2023396.KlZ2vcFHjT@leap>
On Tue, Feb 08, 2022 at 09:56:51AM +0100, Fabio M. De Francesco wrote:
> On martedì 8 febbraio 2022 09:26:26 CET Greg KH wrote:
> > On Tue, Feb 08, 2022 at 09:09:10AM +0100, Fabio M. De Francesco wrote:
> > > On martedì 8 febbraio 2022 00:42:10 CET Leonardo Araujo wrote:
> > > > This patch fixes the following checkpatch.pl warning:
> > > >
> > > > CHECK: 'associcated' may be misspelled - perhaps 'associated'?
> > > >
> > > > Signed-off-by: Leonardo Araujo <leonardo.aa88@gmail.com>
> > > > ---
> > > > drivers/staging/r8188eu/core/rtw_ap.c | 6 +++---
> > > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > > >
> > > "Staging: r8188eu: core: 'associated' may be misspelled - perhaps 'associated'?"
> > > it's not the way patch subjects are created for inclusion in Linux.
> >
> > I do not see anything wrong with this. What do you think is not
> > acceptable?
>
> My opinion is that the formal construction of a patch is important not less than
> the code in it. However it's not that big deal, in this case. But for what my
> opinion is worth, having a subject that says what the patch must do and using an
> imperative language is quite important.
No, the imperative language rule is pointless bureaucracy. Very few of
us are English majors and a lot speak English as a second language. Why
put artificial barriers in the way? You will lose developers like that.
What matters in a commit message is can you understand what the problem
is, how it affects users and how are we going to fix it.
regards,
dan carpenter
prev parent reply other threads:[~2022-02-08 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 23:42 [PATCH] Staging: r8188eu: core: 'associcated' may be misspelled - perhaps 'associated'? Leonardo Araujo
2022-02-08 8:09 ` Fabio M. De Francesco
2022-02-08 8:26 ` Greg KH
2022-02-08 8:56 ` Fabio M. De Francesco
2022-02-08 10:54 ` Dan Carpenter [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=20220208105433.GI1951@kadam \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=leonardo.aa88@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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).