linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Andy Shevchenko' <andy.shevchenko@gmail.com>,
	Jiri Slaby <jirislaby@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: RE: [PATCH v1 1/3] vt: keyboard, use GENMAASK()/BIT() macros instead of open coded variants
Date: Mon, 9 Nov 2020 10:20:42 +0000	[thread overview]
Message-ID: <88282a0514984e2b943628f1476c3bbd@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHp75VeO6inzfRGSEBWgW0OCzjE9uT6LoXeQzHDdg4FiRemYWQ@mail.gmail.com>

From: Andy Shevchenko 
> Sent: 09 November 2020 10:10
> 
> On Mon, Nov 9, 2020 at 11:57 AM Jiri Slaby <jirislaby@kernel.org> wrote:
> > On 06. 11. 20, 17:06, Andy Shevchenko wrote:
> > > On Fri, Nov 6, 2020 at 5:35 PM David Laight <David.Laight@aculab.com> wrote:
> > >> From: Andy Shevchenko
> > >>> Sent: 06 November 2020 14:36
> > >>>
> > >>> There are few places when GENMASK() or BIT() macro is suitable and makes code
> > >>> easier to understand.
> 
> Thanks for the review, my answers below.
> 
> > >> ...
> > >>> -     if ((d & ~0xff) == BRL_UC_ROW) {
> > >>> -             if ((ch & ~0xff) == BRL_UC_ROW)
> > >>> +     if ((d & ~GENMASK(7, 0)) == BRL_UC_ROW) {
> > >>> +             if ((ch & ~GENMASK(7, 0)) == BRL_UC_ROW)
> > >>>                        return d | ch;
> > >>
> > >> Do you really think that makes it more readable?
> > >
> > > Yes. Because this tells explicitly how many bits are used for metadata
> > > vs. data.
> >
> > No, because ~0xff is clearly what it is. GENMASK(7, 0) is:
> > 1) longer to read & parse by brain with result: "GENMASK undefined"
> > 2) terrible in this particular use case
> 
> Maybe #define with a proper name can bring some shed of light here?

Possibly.

> > Another instance of an even worse switch:
> > -               if (arg & ~0x77)
> > +               if (arg & ~(GENMASK(6, 4) | GENMASK(2, 0)))
> 
> It exactly shows what bits we are accepting and what are not. 0x77 you
> need to translate to the bitmap and then figure out the bit numbers.
> This is error prone as shown in some cases.

We all know what 0xff and 0x77 mean.
It is ingrained from years of writing software.

Now it may be that the 0x77 is related to masking off
some other bit values.
In that case you could have a named constant based on the
names of the other bit values.
But if you are putting in simple constants there is nothing
wrong with hex.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2020-11-09 10:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 14:35 [PATCH v1 1/3] vt: keyboard, use GENMAASK()/BIT() macros instead of open coded variants Andy Shevchenko
2020-11-06 14:35 ` [PATCH v1 2/3] vt: keyboard, replace numbers with \r, \n where appropriate Andy Shevchenko
2020-11-09  9:58   ` Jiri Slaby
2020-11-06 14:35 ` [PATCH v1 3/3] vt: keyboard, make use of assign_bit() API Andy Shevchenko
2020-11-09  9:58   ` Jiri Slaby
2020-11-06 15:33 ` [PATCH v1 1/3] vt: keyboard, use GENMAASK()/BIT() macros instead of open coded variants David Laight
2020-11-06 16:06   ` Andy Shevchenko
2020-11-09  9:57     ` Jiri Slaby
2020-11-09 10:10       ` Andy Shevchenko
2020-11-09 10:20         ` David Laight [this message]
2020-11-09 10:44           ` 'Andy Shevchenko'
2020-11-09 10:27         ` Andy Shevchenko
2020-11-09 10:41           ` Jiri Slaby
2020-11-09 10:54             ` Andy Shevchenko

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=88282a0514984e2b943628f1476c3bbd@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).