From: Pavel Machek <pavel@ucw.cz>
To: jayakumar.acpi@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH/RFC 2.6.17-rc4 1/1] ACPI: Atlas ACPI driver v2
Date: Mon, 22 May 2006 02:55:02 +0200 [thread overview]
Message-ID: <20060522005501.GA25434@elf.ucw.cz> (raw)
In-Reply-To: <200605190153.k4J1rW0U002537@localhost.localdomain>
Hi!
> +static int atlas_setup_input(void)
> +{
> + int err;
> +
> + input_dev = input_allocate_device();
> + if (!input_dev) {
> + printk(KERN_ERR "atlas: insufficient mem to allocate input device\n");
> + return -ENOMEM;
> + }
> +
> + input_dev->name = "Atlas ACPI button driver";
> + input_dev->phys = "acpi/input0";
> + input_dev->id.bustype = BUS_HOST;
> + input_dev->evbit[LONG(EV_KEY)] = BIT(EV_KEY);
> + set_bit(KEY_F1 ,input_dev->keybit);
", " please... and are you sure you want it as a F1..F9 keys?
> +/* button handling code */
> +static acpi_status acpi_atlas_button_setup(acpi_handle region_handle,
> + u32 function, void *handler_context, void **return_context)
> +{
> + *return_context =
> + (function != ACPI_REGION_DEACTIVATE) ? handler_context : NULL;
Too many spaces after ? I'd say.
> +static struct acpi_driver atlas_acpi_driver = {
> + .name = ACPI_ATLAS_NAME,
> + .class = ACPI_ATLAS_CLASS,
> + .ids = ACPI_ATLAS_BUTTON_HID,
> + .ops = {
> + .add = atlas_acpi_button_add,
> + .remove = atlas_acpi_button_remove,
> + },
> +};
Watch that whitespace...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-05-22 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 1:53 jayakumar.acpi
2006-05-22 0:55 ` Pavel Machek [this message]
2006-05-22 3:08 ` Jaya Kumar
2006-05-22 0:56 ` Pavel Machek
2006-05-23 13:41 Yu, Luming
2006-05-23 14:01 ` Jaya Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060522005501.GA25434@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=jayakumar.acpi@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®