[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180425120530.zxodrjx3r3i6aipu@localhost>
Date: Wed, 25 Apr 2018 13:05:30 +0100
From: Javier Arteaga <javier@...tex.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Lee Jones <lee.jones@...aro.org>, Dan O'Donovan <dan@...tex.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, linux-gpio@...r.kernel.org,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH RESEND 1/3] mfd: upboard: Add UP2 platform controller
driver
Hi Mika,
On Wed, Apr 25, 2018 at 12:51:41PM +0300, Mika Westerberg wrote:
> On Sat, Apr 21, 2018 at 09:50:07AM +0100, Javier Arteaga wrote:
> > +static const struct acpi_device_id upboard_acpi_match[] = {
> > + { "AANT0F01", (kernel_ulong_t) &upboard_up2_data },
>
> No space after cast so write it like,
>
> { "AANT0F01", (kernel_ulong_t)&upboard_up2_data },
> > + upboard_data = (const struct upboard_data *) id->driver_data;
>
> Ditto and to other places.
Thanks! I've fixed it for the next series now.
Actually, checkpatch did not catch this one, and I can't see an explicit
mention to this rule in coding-style.rst either. Is this worth sending a
patch to the style guide?
> Otherwise looks good to me.
Thanks for your review!
Powered by blists - more mailing lists