From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Johan Hovold <johan@kernel.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Kent Gibson <warthog618@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/1] gpiolib: Introduce for_each_gpio_desc_if() macro
Date: Thu, 20 May 2021 12:16:20 +0300 [thread overview]
Message-ID: <YKYo5EBBDbSDiIwD@smile.fi.intel.com> (raw)
In-Reply-To: <YKYe4rgGTDRfq+va@hovoldconsulting.com>
On Thu, May 20, 2021 at 10:33:38AM +0200, Johan Hovold wrote:
> On Thu, May 20, 2021 at 11:15:31AM +0300, Andy Shevchenko wrote:
> > On Thu, May 20, 2021 at 11:07 AM Johan Hovold <johan@kernel.org> wrote:
> > > On Tue, May 18, 2021 at 11:33:39AM +0300, Andy Shevchenko wrote:
>
> > > The _if suffix here is too vague.
> > >
> > > Please use a more descriptive name so that you don't need to look at the
> > > implementation to understand what the macro does.
> > >
> > > Perhaps call it
> > >
> > > for_each_gpio_desc_with_flag()
> >
> > Haha, I have the same in my internal tree, but then I have changed to
> > _if and here is why:
> > - the API is solely for internal use (note, internals of struct
> > gpio_desc available for the same set of users)
>
> That's not a valid argument here. You should never make code harder to
> read.
>
> There are other ways of marking functions as intended for internal use
> (e.g. do not export them and add a _ prefix or whatever).
>
> > - the current users do only same pattern
>
> That's not an argument against using a descriptive name. Possibly
> against adding a generic for_each_gpio_desc() macro.
>
> > - I don't expect that we will have this to be anything else in the future
>
> Again, irrelevant. Possibly an argument against adding another helper in
> the first place.
>
> > Thus, _if is a good balance between scope of use and naming.
>
> No, no, no. It's never a good idea to obfuscate code.
>
> > I prefer to leave it as is.
>
> I hope you'll reconsider, or that my arguments can convince the
> maintainers to step in here.
>
> > > or just add the more generic macro
> > >
> > > for_each_gpio_desc()
> > >
> > > and open-code the test so that it's clear what's going on here.
>
> FWIW, NAK due to the non-descriptive for_each_desc_if() name.
Btw, missed argument
..._with_flag(..., FLAG_...)
breaks the DRY principle. If you read current code it's clear with that
_if(..., FLAG_...)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-05-20 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 8:33 [PATCH v2 1/1] gpiolib: Introduce for_each_gpio_desc_if() macro Andy Shevchenko
2021-05-18 23:41 ` Linus Walleij
2021-05-20 8:07 ` Johan Hovold
2021-05-20 8:15 ` Andy Shevchenko
2021-05-20 8:33 ` Johan Hovold
2021-05-20 9:03 ` Andy Shevchenko
2021-05-20 9:07 ` Andy Shevchenko
2021-05-20 9:16 ` Andy Shevchenko [this message]
2021-05-20 9:41 ` Johan Hovold
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=YKYo5EBBDbSDiIwD@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.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;
as well as URLs for NNTP newsgroup(s).