[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141028052517.GG60814@vmdeb7>
Date: Mon, 27 Oct 2014 22:25:17 -0700
From: Darren Hart <dvhart@...radead.org>
To: Frans Klaver <fransklaver@...il.com>
Cc: Corentin Chary <corentin.chary@...il.com>,
acpi4asus-user@...ts.sourceforge.net,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/8] eeepc-laptop: clean up control flow in
eeepc_acpi_notify
On Wed, Oct 22, 2014 at 09:12:40PM +0200, Frans Klaver wrote:
> eeepc_acpi_notify increases the indentation level to a whopping four. If
> we revise the conditions a bit, we can reduce that to a more soothing
> two and satisfy the indentation guidelines in Documentation/CodingStyle.
>
> Remove an unwanted space while we're in the neighbourhood.
>
> Signed-off-by: Frans Klaver <fransklaver@...il.com>
> ---
> drivers/platform/x86/eeepc-laptop.c | 53 ++++++++++++++++++-------------------
> 1 file changed, 26 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c
> index 73e8d39..21ffe1f 100644
> --- a/drivers/platform/x86/eeepc-laptop.c
> +++ b/drivers/platform/x86/eeepc-laptop.c
> @@ -1213,7 +1213,7 @@ static void eeepc_input_exit(struct eeepc_laptop *eeepc)
> static void eeepc_input_notify(struct eeepc_laptop *eeepc, int event)
> {
> if (!eeepc->inputdev)
> - return ;
> + return;
> if (!sparse_keymap_report_event(eeepc->inputdev, event, 1, true))
> pr_info("Unknown key %x pressed\n", event);
> }
> @@ -1222,6 +1222,7 @@ static void eeepc_acpi_notify(struct acpi_device *device, u32 event)
> {
> struct eeepc_laptop *eeepc = acpi_driver_data(device);
> u16 count;
> + int old_brightness, new_brightness;
Variable declarations in order of decreasing line length please.
Otherwise, looks good. Mind sending an update of this one?
--
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists