From: Ingo Molnar <mingo@elte.hu>
To: Takashi Iwai <tiwai@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jordan Crouse <jordan.crouse@amd.com>,
Andres Salomon <dilinger@debian.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 - Make CONFIG_OLPC dependent on CONFIG_MGEODE_LX
Date: Tue, 11 Nov 2008 15:04:06 +0100 [thread overview]
Message-ID: <20081111140406.GA3244@elte.hu> (raw)
In-Reply-To: <s5hwsfapdoj.wl%tiwai@suse.de>
* Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 11 Nov 2008 14:53:06 +0100,
> Ingo Molnar wrote:
> >
> >
> > * Takashi Iwai <tiwai@suse.de> wrote:
> >
> > > At Tue, 11 Nov 2008 13:54:02 +0100,
> > > Ingo Molnar wrote:
> > > >
> > > >
> > > > * Takashi Iwai <tiwai@suse.de> wrote:
> > > >
> > > > > The OLPC-specpfic codes require geode_gpio_*() functions although
> > > > > these functions are defined only with CONFIG_MGEODE_LX=y.
> > > > > Add a proper dependency to fix build errors.
> > > > >
> > > > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > > >
> > > > hm, could you please send a .config that shows the build errors?
> > >
> > > Here it is. It's for today's linux-next.
> >
> > hm, which tree did that build failure in linux-next originate from?
> > Your config builds fine here with the latest x86 tree.
>
> Ah, sorry, forgot to mention that the build error comes from the
> latest ALSA code. It contains an OLPC-specific code that is enabled
> via CONFIG_OLPC like:
>
> snd-cs5535audio-$(CONFIG_OLPC) += cs5535audio_olpc.o
>
> where this includes geode_gpio_*() calls.
>
> Of course, I can add an if in Makefile or create a new Kconfig, but
> since asm/olpc.h itself includes asm/geode.h and contains
> geode_gpio*() calls, it would be a proper fix to make CONFIG_OLPC
> dependent on geode.
ah, okay, agreed - i was worried whether this is something affecting
v2.6.28 or slipping through our testing before commits hit linux-next.
I've queued up your fix in tip/x86/kconfig, thanks Takashi!
Ingo
next prev parent reply other threads:[~2008-11-11 14:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 12:23 [PATCH] x86 - Make CONFIG_OLPC dependent on CONFIG_MGEODE_LX Takashi Iwai
2008-11-11 12:54 ` Ingo Molnar
2008-11-11 13:45 ` Takashi Iwai
2008-11-11 13:53 ` Ingo Molnar
2008-11-11 13:58 ` Takashi Iwai
2008-11-11 14:04 ` Ingo Molnar [this message]
2008-11-10 4:17 ` Andres Salomon
2008-11-12 10:53 ` Takashi Iwai
2008-11-12 17:04 ` Andres Salomon
2008-11-12 13:54 ` Jeremy Katz
2008-11-12 14:29 ` Takashi Iwai
2008-11-13 3:44 ` Jeremy Katz
2008-11-13 6:54 ` Takashi Iwai
2008-11-13 15:37 ` Pavel Machek
2008-11-13 15:54 ` Takashi Iwai
2008-11-13 16:14 ` [PATCH] ALSA: cs5535audio: only build OLPC support if MGEODE_LX is defined Andres Salomon
2008-11-13 16:31 ` Takashi Iwai
2008-11-13 17:12 ` Takashi Iwai
2008-11-13 16:38 ` Pavel Machek
2008-11-13 16:42 ` Takashi Iwai
2008-11-13 17:01 ` Andres Salomon
2008-11-13 19:03 ` Ingo Molnar
2008-11-13 23:30 ` Takashi Iwai
2008-11-14 2:38 ` Andres Salomon
2008-11-14 6:54 ` Takashi Iwai
2008-11-14 7:52 ` Pavel Machek
2008-11-14 17:34 ` Jordan Crouse
2008-11-14 18:45 ` Jeremy Katz
2008-11-14 19:24 ` Jordan Crouse
2008-11-14 21:10 ` Andres Salomon
2008-12-10 16:49 ` Takashi Iwai
2008-12-10 18:41 ` Andres Salomon
2008-12-11 7:08 ` Takashi Iwai
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=20081111140406.GA3244@elte.hu \
--to=mingo@elte.hu \
--cc=dilinger@debian.org \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tiwai@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