From: "Jaya Kumar" <jayakumar.acpi@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
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 11:08:28 +0800 [thread overview]
Message-ID: <756b48450605212008m76e93eeav35d0e0bc8cfa9979@mail.gmail.com> (raw)
In-Reply-To: <20060522005501.GA25434@elf.ucw.cz>
On 5/22/06, Pavel Machek <pavel@ucw.cz> wrote:
> > + set_bit(KEY_F1 ,input_dev->keybit);
>
> ", " please... and are you sure you want it as a F1..F9 keys?
Will correct the ",", it was a typo. I picked F1 through F9 because
distributors are free to label the fascia of the panel as they wish. I
figured F1 through F9 would be a sufficiently generic selection. What
do you recommend?
> > +/* 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.
Agreed. Will correct.
>
> > +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...
Done. And I'll remove that proc define.
Thanks,
jayakumar
> 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 3:08 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
2006-05-22 3:08 ` Jaya Kumar [this message]
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=756b48450605212008m76e93eeav35d0e0bc8cfa9979@mail.gmail.com \
--to=jayakumar.acpi@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®