public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: yakui_zhao <yakui.zhao@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Norbert Preining <preining@logic.at>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Eric Anholt <eric@anholt.net>, "Zhang, Rui" <rui.zhang@intel.com>,
	Keith Packard <keithp@keithp.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: 2.6.30-rc3 video/i915 build error
Date: Fri, 24 Apr 2009 09:10:58 +0800	[thread overview]
Message-ID: <1240535458.3651.63.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904231550020.15830@localhost.localdomain>

On Fri, 2009-04-24 at 03:50 +0800, Len Brown wrote:

Hi, Len
    The issue can be fixed by the patch from Matthew.
    In Matthew's patch the acpi video is also selected when the i915 is
compiled as builtin-kernel module.
    But IMO this is not very good. From the Kconfig file we know that
acpi video driver depends on the following configuration:
    BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL

    If the VIDEO_OUTPUT_CONTROL/BACKLIGHT_CLASS_DEVICE is not selected,
then it will still fail in kernel compilation.

    Thanks.
> 
> http://patchwork.kernel.org/patch/18420/
> 
> thanks,
> Len Brown, Intel Open Source Technology Center
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-04-24  1:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 16:36 2.6.30-rc3 video/i915 build error Len Brown
2009-04-23 16:46 ` Norbert Preining
2009-04-23 19:50   ` Len Brown
2009-04-24  1:10     ` yakui_zhao [this message]
2009-04-24  1:57       ` Len Brown
2009-04-24  3:46         ` yakui_zhao
2009-04-24 15:49           ` Len Brown
2009-04-28  6:02             ` yakui_zhao
2009-04-24 15:13         ` Len Brown
2009-04-30 18:07     ` Norbert Preining
2009-04-30 18:12       ` Norbert Preining

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=1240535458.3651.63.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=rui.zhang@intel.com \
    /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