From: Randy Dunlap <randy.dunlap@oracle.com>
To: Joey Lee <jlee@novell.com>
Cc: mjg@redhat.com, mjg59@srcf.ucam.org, gregkh@suse.de,
trenn@suse.de, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, Dennis.Jansen@web.de
Subject: Re: [PATCH] Add Intel Poulsbo Stub Driver
Date: Fri, 10 Sep 2010 08:02:09 -0700 [thread overview]
Message-ID: <4C8A4871.9040103@oracle.com> (raw)
In-Reply-To: <4C8A4285020000230002020B@novprvlin0050.provo.novell.com>
On 09/09/10 21:36, Joey Lee wrote:
>>> + # Poulsbo stub depends on ACPI_VIDEO when ACPI is enabled
>>> + # but for select to work, need to select ACPI_VIDEO's dependencies, ick
>>> + select ACPI_VIDEO if ACPI
>>
>> What does it do when ACPI is not enabled? Does the driver even build
>> when APCI is not enabled? (given the acpi_video* calls in it)
>>
>
> This driver will not do anything if API is not enabled. It only call
> acpi_video_register/acpi_video_unregister, and acpi/video.h handle it
> like the following:
>
> #if (defined CONFIG_ACPI_VIDEO || defined CONFIG_ACPI_VIDEO_MODULE)
> extern int acpi_video_register(void);
> extern void acpi_video_unregister(void);
> extern int acpi_video_get_edid(struct acpi_device *device, int type,
> int device_id, void **edid);
> #else
> static inline int acpi_video_register(void) { return 0; }
> static inline void acpi_video_unregister(void) { return; }
> static inline int acpi_video_get_edid(struct acpi_device *device, int
> type,
> int device_id, void **edid)
> {
> return -ENODEV;
> }
> #endif
>
> So, I think don't need add "depends on ACPI_VIDEO". How do you think?
Yes, OK, I see. Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-10 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 4:36 [PATCH] Add Intel Poulsbo Stub Driver Joey Lee
2010-09-10 15:02 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 7:34 Joey Lee
2010-10-19 12:33 ` Matthew Garrett
2010-09-19 16:35 Joey Lee
2010-09-15 14:24 Lee, Chun-Yi
2010-09-14 18:07 Joey Lee
2010-09-14 18:10 ` Matthew Garrett
2010-09-14 18:30 ` Valdis.Kletnieks
2010-09-14 2:39 Lee, Chun-Yi
2010-09-14 17:10 ` Valdis.Kletnieks
2010-09-10 10:03 Joey Lee
2010-09-10 4:53 Joey Lee
2010-09-01 9:08 Lee, Chun-Yi
2010-09-01 15:00 ` Greg KH
2010-09-01 17:11 ` Randy Dunlap
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=4C8A4871.9040103@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Dennis.Jansen@web.de \
--cc=gregkh@suse.de \
--cc=jlee@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mjg@redhat.com \
--cc=trenn@suse.de \
/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