From: Karolina Drobnik <karolinadrobnik@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>, Joe Perches <joe@perches.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
forest@alittletooquiet.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] Re: [PATCH] staging: vt6655: Rename `dwAL2230InitTable` array
Date: Wed, 20 Oct 2021 16:56:18 +0100 [thread overview]
Message-ID: <596fba87187b73277fd5c1102baa1815ed8fe4f8.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110201615590.2930@hadrien>
On Wed, 2021-10-20 at 07:09 -0700, Joe Perches wrote:
> On Wed, 2021-10-20 at 06:44 -0700, Joe Perches wrote:
> > In this file there are more than 100 uses of
> >
> > (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW
> >
> > Maybe add a define for it and substitute the uses for the define.
>
> Look at the code too.
>
> It looks as if every use of IFRFbWriteEmbedded() has this added to
> the 2nd argument and that the 2nd argument isn't used anywhere else.
>
> Maybe remove it altogether and add it to IFRFbWriteEmbedded().
>
> And it looks as if the + uses for these should logically be |
Sounds like a very good idea. I'll add it to my to-do list, thanks :)
On Wed, 2021-10-20 at 16:16 +0200, Julia Lawall wrote:
> Karolina,
>
> If more than a hundred such changes are necessary, you may find
> Coccinelle
> useful: https://coccinelle.gitlabpages.inria.fr/website/
Hmm, I'll check this out, it may come in handy.
Thanks,
Karolina
prev parent reply other threads:[~2021-10-20 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 13:28 [PATCH] staging: vt6655: Rename `dwAL2230InitTable` array Karolina Drobnik
2021-10-20 13:44 ` Joe Perches
2021-10-20 14:09 ` Joe Perches
2021-10-20 14:16 ` [Outreachy kernel] " Julia Lawall
2021-10-20 15:56 ` Karolina Drobnik [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=596fba87187b73277fd5c1102baa1815ed8fe4f8.camel@gmail.com \
--to=karolinadrobnik@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=julia.lawall@inria.fr \
--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