From mboxrd@z Thu Jan 1 00:00:00 1970 From: Javier Arteaga Subject: Re: [RFC PATCH RESEND 1/3] mfd: upboard: Add UP2 platform controller driver Date: Wed, 25 Apr 2018 13:05:30 +0100 Message-ID: <20180425120530.zxodrjx3r3i6aipu@localhost> References: <20180421085009.28773-1-javier@emutex.com> <20180421085009.28773-2-javier@emutex.com> <20180425095141.GL2173@lahna.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20180425095141.GL2173@lahna.fi.intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Mika Westerberg Cc: Lee Jones , Dan O'Donovan , Andy Shevchenko , Heikki Krogerus , Linus Walleij , Jacek Anaszewski , Pavel Machek , linux-gpio@vger.kernel.org, linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-gpio@vger.kernel.org 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!