From: Joe Perches <joe@perches.com>
To: Rodolfo C Villordo <rodolfovillordo@gmail.com>,
Julia Lawall <julia.lawall@inria.fr>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Forest Bond <forest@alittletooquiet.net>,Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel@driverdev.osuosl.org,linux-kernel@vger.kernel.org
Date: Mon, 08 Jun 2020 16:33:06 -0700 [thread overview]
Message-ID: <c25f5af83658ab9ef4ae8ef3825ea6540fe4e094.camel@perches.com> (raw)
In-Reply-To: <20200608225838.GA26559@ip-172-31-24-31.ec2.internal>
On Mon, 2020-06-08 at 22:58 +0000, Rodolfo C Villordo wrote:
> On Mon, Jun 08, 2020 at 01:41:11AM -0700, Joe Perches wrote:
> > On Mon, 2020-06-08 at 07:59 +0200, Julia Lawall wrote:
> > > On Mon, 8 Jun 2020, Al Viro wrote:
> > >
> > > > On Sun, Jun 07, 2020 at 10:41:56PM +0000, Rodolfo C. Villordo wrote:
> > > > > Multiple line over 80 characters fixes by splitting in multiple lines.
> > > > > Warning found by checkpatch.pl
> > > >
> > > > I doubt that checkpatch.pl can catch the real problems there:
> > > >
> > > > * Hungarian Notation Sucks. Really.
> > > > * so does CamelCase, especially for wonders like s_uGetRTSCTSRsvTime
>
> Yes, I agree with that.
>
> > > Rodolfo,
> > >
> > > If you work hard with Coccinelle and python scripting, it can help with
> > > the first two problems.
> >
> > These VIA vt6655/vt6656 drivers have been in staging for more than
> > a decade. There are relatively few checkpatch coding style
> > cleanups to do but there are many overall style issues to resolve.
> >
>
> Yes, vt6655/rxtx.c needs lots of work. I was avoiding submit bigger changes
> because this is my second patch submission.
>
> Thank you all for the comments. I'm really sorry for the odd subject.
>
> How should I move forward with this?
>
> 1 - Update this patch with the changes pointed by Dan Carpenter?
Keep your changes small until you really know how this
style of linux kernel staging changes is done.
> 2 - Do a more elaborated and bigger change, like suggested by Al Viro
> and Joe Perches?
A patch series is much preferred to a single large change.
If you decide to refactor various functions, please do that
in separate, discrete patches.
Adding a #define and doing a sed like:
$ sed -i 's/(BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW/AL2230_RLEN_CTL/' drivers/staging/vt6655/*.[ch]
should be a single patch.
And if you do that, another should be done for AL7230
$ sed -i 's/(BY_AL7230_REG_LEN << 3) + IFREGCTL_REGW/AL7230_RLEN_CTL/' drivers/staging/vt6655/*.[ch]
etc...
Maybe the #define BY_AL2230_REG_LEN should be 0x17 so that
the << 3 is more obviously constrained to the low byte
Maybe the + uses in the macros should be bitwise |.
Go wild after you figure out the process, just keep your
patches to obvious, small and verifiable changes.
next prev parent reply other threads:[~2020-06-08 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 22:41 Rodolfo C. Villordo
2020-06-08 5:15 ` Greg Kroah-Hartman
2020-06-08 5:46 ` Al Viro
2020-06-08 5:59 ` Julia Lawall
2020-06-08 8:41 ` Joe Perches
[not found] ` <20200608225838.GA26559@ip-172-31-24-31.ec2.internal>
2020-06-08 23:33 ` Joe Perches [this message]
2020-06-10 19:20 ` Rodolfo C Villordo
2020-06-08 7:26 ` Dan Carpenter
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=c25f5af83658ab9ef4ae8ef3825ea6540fe4e094.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rodolfovillordo@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome