public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arun Raghavan <arun.raghavan@collabora.co.uk>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apple-gmux: Correctly depend on apple_bl for building
Date: Thu, 28 Jun 2012 18:53:35 +0530	[thread overview]
Message-ID: <1340889815.4994.4.camel@localhost> (raw)
In-Reply-To: <20120628132058.GA15308@thinkpad-t410>

On Thu, 2012-06-28 at 08:20 -0500, Seth Forshee wrote:
> On Thu, Jun 28, 2012 at 04:06:36PM +0530, Arun Raghavan wrote:
> > apple_bl_register/unregister() are unconditionally used now, so we need
> > to make sure that apple_bl is selected appropriately (built-in/module)
> > if apple-gmux is being built.
> 
> apple_bl.h provides stubs for these functions when apple_bl is not
> built, so this shouldn't be necessary. Are you encoutering a situation
> that causes build problems?

Yes, I am. With CONFIG_BACKLIGHT_APPLE=m and CONFIG_APPLE_GMUX=y, I see
the following error:

  LD      init/built-in.o
drivers/built-in.o: In function `gmux_probe':
apple-gmux.c:(.devinit.text+0xa769): undefined reference to `apple_bl_unregister'
drivers/built-in.o: In function `gmux_remove':
apple-gmux.c:(.devexit.text+0x46d): undefined reference to `apple_bl_register'

-- Arun


  reply	other threads:[~2012-06-28 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 10:36 [PATCH] apple-gmux: Correctly depend on apple_bl for building Arun Raghavan
2012-06-28 13:20 ` Seth Forshee
2012-06-28 13:23   ` Arun Raghavan [this message]
2012-06-28 13:48     ` Seth Forshee
2012-06-28 13:50       ` Seth Forshee
2012-06-28 13:51       ` Arun Raghavan
2012-06-28 15:15         ` Seth Forshee

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=1340889815.4994.4.camel@localhost \
    --to=arun.raghavan@collabora.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=seth.forshee@canonical.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