linux-kernel - Re: [PATCH] misc,acpi,backlight: MSI S270 Laptop support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061002184840.e5c090f2.akpm@osdl.org>
Date:	Mon, 2 Oct 2006 18:48:40 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Lennart Poettering <mzxreary@...inter.de>
Cc:	len.brown@...el.com, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, s270-linux@...l.0pointer.de
Subject: Re: [PATCH] misc,acpi,backlight: MSI S270 Laptop support

On Tue, 3 Oct 2006 03:10:56 +0200
Lennart Poettering <mzxreary@...inter.de> wrote:

> From: Lennart Poettering <mzxreary@...inter.de>
> 
> A driver for the special features of MSI S270 laptops (and maybe other
> MSI laptops). This driver implements a backlight device for
> controlling LCD brightness (/sys/class/backlight/msi-laptop-bl/).  In
> addition it allows access to the WLAN and Bluetooth states through a
> platform driver (/sys/devices/platform/msi-laptop-pf/).
> 
> ...
>

err, this driver has only about fifteen tab characters in it.  The whole
thing is using lean-on-the-spacebar instead of hard tabs.

fix, please??

> +static ssize_t store_lcd_level(
> +                struct device *dev, struct device_attribute *attr, const char *buf, size_t count) {

No, kernel-style is

static ssize_t store_lcd_level(struct device *dev,
	struct device_attribute *attr, const char *buf, size_t count)
{

or thereabouts.


-
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/