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 v2 0/5] staging: rtl8723bs: Change
Date: Sun, 11 Apr 2021 09:11:43 +0200 [thread overview]
Message-ID: <3154849.IkRRYng9eG@localhost.localdomain> (raw)
In-Reply-To: <YHKZlqFy15QC9Mzz@kroah.com>
On Sunday, April 11, 2021 8:39:18 AM CEST Greg KH wrote:
> On Sat, Apr 10, 2021 at 05:00:03PM +0200, Fabio M. De Francesco wrote:
> > Remove camelcase, correct misspelled words in comments, remove an
> > unused
> > variable, change the type of a variable and its use, change comparisons
> > with 'true' in controlling expressions.
> >
> > Changes from v1: Fix a typo in subject of patch 1/5, add patch 5/5.
>
> The subject line above is very odd :(
>
True. I've just read the output of git format in /tmp and noticed that the
line with the "subject" was broken in two different one. I think I had
pressed return while editing.
I'm about to send that series again with v3.
In the while I noticed you sent a note to let me know that the you have
added the patch titled "staging: rtl8723bs: core: Remove an unused
variable" to your staging git tree.
I think this could be a potential issue because the same patch is in the
series that I have to send anew. I put that patch in the series because
yesterday you wrote that the message with subject "Outreachy patches caught
up on.", asking to rebase and resend.
However, I'm about to send v3 of this patchset. I have no idea whether or
not you will have problems in applying that. If you have problems with it,
please let me know.
Thanks,
Fabio
next prev parent reply other threads:[~2021-04-11 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 15:00 [Outreachy kernel] [PATCH v2 0/5] staging: rtl8723bs: Change Fabio M. De Francesco
2021-04-10 15:00 ` [Outreachy kernel] [PATCH v2 1/5] staging: rtl8723bs: Remove camelcase in several files Fabio M. De Francesco
2021-04-10 15:00 ` [Outreachy kernel] [PATCH v2 2/5] staging: rtl8723bs: include: Fix misspelled words in comments Fabio M. De Francesco
2021-04-11 6:40 ` Greg KH
2021-04-10 15:00 ` [Outreachy kernel] [PATCH v2 3/5] staging: rtl8723bs: core: Remove an unused variable Fabio M. De Francesco
2021-04-10 15:00 ` [Outreachy kernel] [PATCH v2 4/5] staging: rtl8723bs: Change the type and use of a variable Fabio M. De Francesco
2021-04-10 15:00 ` [Outreachy kernel] [PATCH v2 5/5] staging: rtl8723bs: core: Change a controlling expression Fabio M. De Francesco
2021-04-11 6:39 ` [Outreachy kernel] [PATCH v2 0/5] staging: rtl8723bs: Change Greg KH
2021-04-11 7:11 ` Fabio M. De Francesco [this message]
2021-04-11 7:17 ` Greg KH
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=3154849.IkRRYng9eG@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