From: Julia Lawall <julia.lawall@inria.fr>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Re: [PATCH] Correct indentation in Hal8723BReg.h
Date: Tue, 6 Apr 2021 08:40:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2104060839310.2882@hadrien> (raw)
In-Reply-To: <1851038.q9TLUjBrch@localhost.localdomain>
On Tue, 6 Apr 2021, Fabio M. De Francesco wrote:
> On Tuesday, April 6, 2021 7:52:52 AM CEST Fabio M. De Francesco wrote:
> > On Tuesday, April 6, 2021 7:12:20 AM CEST Greg KH wrote:
> > > On Tue, Apr 06, 2021 at 04:08:15AM +0200, Fabio M. De Francesco wrote:
> > > > Correct indentation issues of many #define and comments in Hal8723BReg.h
> > > >
> > > > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > > > ---
> > > > drivers/staging/rtl8723bs/hal/Hal8723BReg.h | 604 ++++++++++----------
> > > > 1 file changed, 302 insertions(+), 302 deletions(-)
> > >
> > > You forgot to cc: all of the needed mailing lists. And your subject
> > > line needs some work. But the biggest issue is that I do not understand
> > > what this patch does at all. What is wrong with the original code here
> > > that required you to "correct" it?
> > >
> > > confused,
> > >
> > > greg k-h
> > >
> > I'm sorry that I forgot to cc linux-staging and linux-kernel mailing lists
> > and for the subject I had already sent a v2 patch that had
> > all the required tags (staging: rtl8723: hal:).
> >
> > I think that what was wrong with the original code was that
> > the #define values were far from the symbols with random indentation.
> >
> > For example, I changed something like:
> > #define SYMB1 0123
> > #define SYMB2 5678
> > #define SYMB3 9ABC
> >
> > to:
> > #define SYMB1 0123
> > #define SYMB2 5678
> > #define SYMB3 9ABC
>
> the preceding defined values are in a single column. I don't understand why KMail show them in different levels of indentation. However, I hope that my argument in support of the patch was still clear.
There is surely a difference with the use of spaces and tabs. If you
change something about the defines and this problem shows up, you can make
another patch in the series to make the spacing more uniform.
julia
next prev parent reply other threads:[~2021-04-06 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 2:08 [PATCH] Correct indentation in Hal8723BReg.h Fabio M. De Francesco
2021-04-06 5:12 ` Greg KH
2021-04-06 5:52 ` Fabio M. De Francesco
2021-04-06 6:00 ` Fabio M. De Francesco
2021-04-06 6:40 ` Julia Lawall [this message]
2021-04-06 7:08 ` [Outreachy kernel] " Fabio M. De Francesco
2021-04-06 7:22 ` Greg KH
2021-04-06 7:27 ` Julia Lawall
2021-04-06 7:46 ` FMDF
2021-04-06 8:01 ` Julia Lawall
2021-04-06 8:38 ` Fabio M. De Francesco
2021-04-06 8:44 ` Julia Lawall
2021-04-06 6:43 ` Julia Lawall
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=alpine.DEB.2.22.394.2104060839310.2882@hadrien \
--to=julia.lawall@inria.fr \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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.