[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkda=xz=6sVuM1r81krR+09gOTaxBkab3_Xj0qMEB5AdVtQ@mail.gmail.com>
Date: Thu, 15 Nov 2018 15:56:27 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Pavel Machek <pavel@....cz>
Cc: "Dan O'Donovan" <dan@...tex.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
linux-leds@...r.kernel.org, carlos.iglesias@...tex.com
Subject: Re: [PATCH v3 1/3] mfd: upboard: Add UP2 platform controller driver
On Sun, Nov 11, 2018 at 12:29 PM Pavel Machek <pavel@....cz> wrote:
>
> > +static void __reg_io_start(const struct upboard_ddata * const ddata)
> > +{
> > + /*
> > + * CLEAR signal must be pulsed low before any register access.
> > + * This resets internal counters in the controller and marks
> > + * the start of a new register access.
> > + */
> > + set_clear(ddata, 0);
> > + set_clear(ddata, 1);
> > +}
>
> We normally reserve __ prefix for different stuff. This is not using
> it appropriately.
+1
I actively dislike __underscore_notation as it seems to be
completely arbitrary and ambiguous. I think even
do_the_stuff_reg_io_start() is better.
But please come up with something to the point and
descriptive! :)
Yours,
Linus Walleij
Powered by blists - more mailing lists