[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2b4f7f38a8a490ffc917f7199099ac95656c8c2.camel@gmail.com>
Date: Mon, 23 Mar 2020 04:48:08 +0530
From: Shreeya Patel <shreeya.patel23498@...il.com>
To: Joe Perches <joe@...ches.com>, Greg KH <gregkh@...uxfoundation.org>
Cc: Larry.Finger@...inger.net, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org, outreachy-kernel@...glegroups.com
Subject: Re: [Outreachy kernel] [PATCH 01/11] Staging: rtl8188eu: hal_com:
Add space around operators
On Sun, 2020-03-22 at 08:09 -0700, Joe Perches wrote:
> On Sun, 2020-03-22 at 12:27 +0100, Greg KH wrote:
Hi Greg and Joe,
> > On Sun, Mar 22, 2020 at 03:51:13AM +0530, Shreeya Patel wrote:
> > > Add space around operators for improving the code
> > > readability.
> > > Reported by checkpatch.pl
> > >
> > > git diff -w shows no difference.
> > > diff of the .o files before and after the changes shows no
> > > difference.
> >
> > There is no need to have these two lines on every changelog comment
> > in
> > this series :(
>
Yes I get that.
> In my opinion, there's no need for a series here.
>
> Whitespace only changes _should_ be done all at once.
>
> Whitespace changes _could_ have changed string constants.
>
> So noting that the patch in only whitespace and that
> there isn't a difference in object files is useful as
> it shows any change has been compiled and tested.
>
Joe, I feel the same thing, there is no need of a patch series
for it but I was given a suggestion that it becomes difficult for the
reviewers to review the patch so it is good to send a patchset instead.
But as you said, we are testing that there is no change in the object
file so we can go ahead with a single patch for all the whitespace
changes.
If you feel this is right then can I go ahead and send a single patch
for it? ( need your or Greg's confirmation before I do it )
Thanks
>
Powered by blists - more mailing lists