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 v3
Date: Mon, 22 May 2006 07:10:46 -0400 [thread overview]
Message-ID: <756b48450605220410w4623fda3p23ddc4b38e64516b@mail.gmail.com> (raw)
In-Reply-To: <20060522093301.GB25624@elf.ucw.cz>
On 5/22/06, Pavel Machek <pavel@ucw.cz> wrote:
> ACK, but I guess you should cc Dmitry (input maintainer) and possibly
> Andrew Morton to get it in... Ok, few more nits.
Will do.
>
> > +#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?
Depends on the application I guess. If CONFIG_INPUT is disabled, then
only applications that read /proc/acpi/event will see the ASIM events.
>
> > + }
> > +
> > + return status ;
>
> Extra " " before ;.
Sorry. Corrected.
>
> > +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 }.
I hope I understood you correctly, the } on .ops after .remove should
align with the . ops right?. I tried to conform with button.c and
others. I will make the change I think you are suggesting anyway since
it seems more natural.
74 static struct acpi_driver acpi_button_driver = {
75 .name = ACPI_BUTTON_DRIVER_NAME,
76 .class = ACPI_BUTTON_CLASS,
77 .ids = "ACPI_FPB,ACPI_FSB,PNP0C0D,PNP0C0C,PNP0C0E",
78 .ops = {
79 .add = acpi_button_add,
80 .remove = acpi_button_remove,
81 },
82 };
71 static struct acpi_driver acpi_video_bus = {
72 .name = ACPI_VIDEO_DRIVER_NAME,
73 .class = ACPI_VIDEO_CLASS,
74 .ops = {
75 .add = acpi_video_bus_add,
76 .remove = acpi_video_bus_remove,
77 .match = acpi_video_bus_match,
78 },
79 };
>
> > +MODULE_SUPPORTED_DEVICE("Atlas ACPI");
>
> Are you sure this si good idea?
You are right. It's a bad idea, none of the other drivers do it. I'll
take it out.
Thanks,
jayakumar
prev parent reply other threads:[~2006-05-22 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 3:33 jayakumar.acpi
2006-05-22 9:33 ` Pavel Machek
2006-05-22 11:10 ` Jaya Kumar [this message]
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=756b48450605220410w4623fda3p23ddc4b38e64516b@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®