linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>,
	platform-driver-x86@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 2 (drivers/platform/x86/apple-gmux.c)
Date: Thu, 2 Aug 2012 11:36:16 -0500	[thread overview]
Message-ID: <20120802163616.GI32395@thinkpad-t410> (raw)
In-Reply-To: <20120802163154.GH32395@thinkpad-t410>

On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
> > On 08/02/2012 09:15 AM, Seth Forshee wrote:
> > 
> > > On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
> > >> On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> Please do not add anything to linux-next included branches/series that is
> > >>> destined for v3.7 until after v3.6-rc1 is released.
> > >>>
> > >>> Reminder: do not rebase your branches before asking Linus to pull them ...
> > >>>
> > >>> Changes since 20120731:
> > >>>
> > >>
> > >>
> > >> when CONFIG_ACPI is not enabled: (on i386)
> > >>
> > >> drivers/platform/x86/apple-gmux.c: In function 'gmux_probe':
> > >> drivers/platform/x86/apple-gmux.c:196:2: error: implicit declaration of function 'acpi_video_dmi_promote_vendor'
> > >> drivers/platform/x86/apple-gmux.c: In function 'gmux_remove':
> > >> drivers/platform/x86/apple-gmux.c:219:2: error: implicit declaration of function 'acpi_video_dmi_demote_vendor'
> > >>
> > >>
> > >> Full randconfig file is attached.
> > > 
> > > I sent Matthew a patch that should fix this [1], but he doesn't seem to
> > > have picked it up yet.
> > > 
> > > Seth
> > > 
> > > [1] https://lkml.org/lkml/2012/7/2/257
> > > 
> > 
> > 
> > That patch does not fix this build error.
> > There is still an implicit assumption in Kconfig and
> > the driver source that ACPI is enabled.
> 
> The functions in question are built or not based off of ACPI_VIDEO,
> which in turn depends on ACPI. So if ACPI=n, then ACPI_VIDEO=n and you
> can't configure APPLE_GMUX=(m|y). Is that right, or am I missing
> something?

Nevermind, I see what I missed.

This is kind of messy -- maybe those declartions should be extracted
from the #ifdef CONFIG_ACPI to avoid this kind of Kconfig madness?

Seth

  parent reply	other threads:[~2012-08-02 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  4:15 linux-next: Tree for Aug 2 Stephen Rothwell
2012-08-02 15:55 ` linux-next: Tree for Aug 2 (dm-raid) Randy Dunlap
2012-08-02 20:34   ` [dm-devel] " NeilBrown
2012-08-02 16:07 ` linux-next: Tree for Aug 2 (drivers/platform/x86/apple-gmux.c) Randy Dunlap
2012-08-02 16:12   ` Matthew Garrett
2012-08-02 16:15   ` Seth Forshee
2012-08-02 16:19     ` Randy Dunlap
2012-08-02 16:31       ` Seth Forshee
2012-08-02 16:35         ` Randy Dunlap
2012-08-02 16:36         ` Seth Forshee [this message]
2012-08-02 16:43           ` Seth Forshee
2012-08-02 16:37         ` Matthew Garrett

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=20120802163616.GI32395@thinkpad-t410 \
    --to=seth.forshee@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).