From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH v7 1/3] staging: rtl8723bs: Remove camelcase in several files
Date: Sat, 10 Apr 2021 11:45:18 +0200 [thread overview]
Message-ID: <3026831.3QyE5GyAct@localhost.localdomain> (raw)
In-Reply-To: <YHFwkJlTNxQwPyN3@kroah.com>
On Saturday, April 10, 2021 11:32:00 AM CEST Greg KH wrote:
> On Sat, Apr 10, 2021 at 11:22:29AM +0200, Fabio M. De Francesco wrote:
> > Remove camelcase in bFwCurrentInPSMode, a variable used by code
> > of several subdirectories/files of the driver. Issue detected by
> > checkpatch.pl. Delete the unnecessary "b" (that stands for "byte") from
> > the beginning of the name.
> >
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > ---
>
> Why is there a "v7" in this subject line, but not all the other lines?
>
It's v7 because only this file (and not the others in the series had six
previous versions that you dropped. Please remind that it was already sent
alone (not in a series) several times. The changelog is in the body.
Should I drop that "v7" and the changelog, and the send the patch series
anew?
Please, I'm waiting your instructions on what to do.
Thanks,
Fabio
>
> It should be in all of them, including the 0/X email, git format-patch
> will create it automatically if you tell it to.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-04-10 9:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 9:22 [Outreachy kernel] [PATCH 0/4] staging: rtl8723bs: Change several files of the driver Fabio M. De Francesco
2021-04-10 9:22 ` [Outreachy kernel] [PATCH v7 1/3] staging: rtl8723bs: Remove camelcase in several files Fabio M. De Francesco
2021-04-10 9:32 ` Greg KH
2021-04-10 9:45 ` Fabio M. De Francesco [this message]
2021-04-10 10:32 ` Greg KH
2021-04-10 9:22 ` [Outreachy kernel] [PATCH 2/4] staging: rtl8723bs: include: Fix misspelled words in comments Fabio M. De Francesco
2021-04-10 9:22 ` [Outreachy kernel] [PATCH 3/4] staging: rtl8723bs: core: Remove an unused variable Fabio M. De Francesco
2021-04-10 9:22 ` [Outreachy kernel] [PATCH 4/4] staging: rtl8723bs: Change the type and use of a variable Fabio M. De Francesco
2021-04-10 9:31 ` Greg KH
2021-04-10 9:56 ` Fabio M. De Francesco
2021-04-10 10:31 ` Greg KH
2021-04-10 10:58 ` Fabio M. De Francesco
2021-04-10 11:03 ` Greg KH
2021-04-10 11:23 ` Fabio M. De Francesco
2021-04-10 11:33 ` Greg KH
2021-04-10 11:37 ` Julia Lawall
2021-04-10 12:01 ` Fabio M. De Francesco
2021-04-10 12:12 ` Julia Lawall
2021-04-10 13:02 ` Fabio M. De Francesco
2021-04-10 13:24 ` Julia Lawall
2021-04-10 13:53 ` Fabio M. De Francesco
2021-04-10 13:55 ` Greg KH
2021-04-10 14:01 ` Julia Lawall
2021-04-10 10:02 ` Julia Lawall
2021-04-10 10:03 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2021-04-09 16:32 [Outreachy kernel] [PATCH v7 1/3] staging: rtl8723bs: Remove camelcase in several files Fabio M. De Francesco
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=3026831.3QyE5GyAct@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.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