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 v3
Date: Mon, 22 May 2006 11:33:01 +0200 [thread overview]
Message-ID: <20060522093301.GB25624@elf.ucw.cz> (raw)
In-Reply-To: <200605220333.k4M3Xkg6020638@localhost.localdomain>
On Po 22-05-06 11:33:46, jayakumar.acpi@gmail.com wrote:
> Hi Len, ACPI, and kernel folk,
>
> Appended is v3 after removing unused defines and whitespace
> cleanup. Thanks to Pavel Machek for the feedback.
>
> Please let me know if it looks okay and if you have any feedback
> or suggestions.
>
> Thanks,
> Jaya Kumar
>
> Signed-off-by: Jaya Kumar <jayakumar.acpi@gmail.com>
ACK, but I guess you should cc Dmitry (input maintainer) and possibly
Andrew Morton to get it in... Ok, few more nits.
> +#else
> +#define atlas_free_input(...)
> +#define atlas_setup_input(...) 0
> +#define atlas_input_report(...)
> +#endif
Does the driver actually do anything useful in this case?
> + }
> +
> + return status ;
Extra " " before ;.
> +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,
> + },
Extra tab before }.
> +MODULE_SUPPORTED_DEVICE("Atlas ACPI");
Are you sure this si good idea?
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 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 3:33 [PATCH/RFC 2.6.17-rc4 1/1] ACPI: Atlas ACPI driver v3 jayakumar.acpi
2006-05-22 9:33 ` Pavel Machek [this message]
2006-05-22 11:10 ` 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=20060522093301.GB25624@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