From: R Veera Kumar <vkor@vkten.in>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [RESEND PATCH 00/10] Correction of typos and long lines of comments
Date: Thu, 19 Mar 2020 22:16:03 +0530 [thread overview]
Message-ID: <20200319164601.GA2240@tulip.local> (raw)
In-Reply-To: <alpine.DEB.2.21.2003191656520.2312@hadrien>
On Thu, Mar 19, 2020 at 04:58:05PM +0100, Julia Lawall wrote:
>
>
> On Thu, 19 Mar 2020, R Veera Kumar wrote:
>
> > Correction of typos and long lines of comments.
> > Misspellings found using checkpatch.pl.
> >
> > ---
> > R Veera Kumar (10):
> > staging: rtl8723bs: hal: Correct a typo in a comment
> > staging: rtl8723bs: hal: Correct a typo in a comment
>
> Maybe you could just put all the typo ones in a single patch? They should
> be easy to check and have no impact on the execution, so it is hard to see
> why one would want to revert them separately.
>
Yes. That's what he meant in reply. But I did otherwise because in my
first patch to mailing list I had typos in two different files. I sent
it as single patch and he accepted. And the I asked him whether it could
have been sent as patchset, and he said yes.
Now reading submitting-patches doc it says if it is single kind of
change then it should be put in one patch. And only if it is logically
different then in two separate patches.
> On the other hand, the patch would be just typos, not long line changes
> mixed in as well.
>
Yeah.
Veera
> julia
>
> >
> > drivers/staging/rtl8723bs/hal/HalBtc8723b1Ant.c | 2 +-
> > drivers/staging/rtl8723bs/hal/HalBtc8723b2Ant.c | 2 +-
> > drivers/staging/rtl8723bs/hal/HalPhyRf.c | 7 +++++--
> > 10 files changed, 27 insertions(+), 18 deletions(-)
> >
prev parent reply other threads:[~2020-03-19 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 11:06 [RESEND PATCH 00/10] Correction of typos and long lines of comments R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 01/10] staging: rtl8723bs: hal: Correct a typo in a comment R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 02/10] " R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 03/10] staging: rtl8723bs: hal: Correct typos and long line of comment R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 04/10] staging: rtl8723bs: hal: Correct a typo and long line of a comment R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 05/10] " R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 06/10] staging: rtl8723bs: hal: Correct typos and long line of comments R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 07/10] staging: rtl8723bs: hal: Correct a typo in a comment R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 08/10] staging: rtl8723bs: hal: Correct typos " R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 09/10] staging: rtl8723bs: hal: Correct a typo " R Veera Kumar
2020-03-19 11:06 ` [RESEND PATCH 10/10] " R Veera Kumar
2020-03-19 12:09 ` Greg Kroah-Hartman
2020-03-19 15:58 ` [Outreachy kernel] [RESEND PATCH 00/10] Correction of typos and long lines of comments Julia Lawall
2020-03-19 16:46 ` R Veera Kumar [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=20200319164601.GA2240@tulip.local \
--to=vkor@vkten.in \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.