public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
	lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] ucb1400_ts depends SND_AC97_BUS
Date: Sun, 10 Dec 2006 20:45:45 -0800	[thread overview]
Message-ID: <20061210204545.a68d15cd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612102244140.2630@xanadu.home>

On Sun, 10 Dec 2006 22:55:25 -0500 (EST) Nicolas Pitre wrote:

> On Sat, 9 Dec 2006, Randy Dunlap wrote:
> 
> > On Sat, 09 Dec 2006 22:17:55 -0500 (EST) Nicolas Pitre wrote:
> > 
> > > Please consider what SND_CONFIG_AC97_BUS corresponds to.  It is 
> > > sound/pci/ac97/ac97_bus.c and if you look into this file you'll see that 
> > > it is perfectly buildable even if sound is entirely configured out, just 
> > > like some lib code would be.
> > 
> > OK.  Should it (CONFIG_SND_AC97_BUS -> sound/pci/ac97/ac97_bus.c)
> > be buildable when sound is disabled?
> 
> Yes.
> 
> > If so, where should it be moved to (since afaik, make won't even
> > descend into sound/ if SOUND=n; I don't see that changing
> > any time soon).
> 
> What about this patch?

About all I can say is that it builds as expected...


> ----- >8
> Subject: break config ordering/dependency between UCB1400 touchscreen driver and sound subsystem
> 
> Commit 2d4ba4a3b9aef95d328d74a17ae84f8d658059e2 introduced a dependency
> that was never meant to exist when the ac97_bus.c module was created.
> Move ac97_bus.c up the directory hierarchy to make sure it is built when 
> selected even if sound is configured out so things work as originally 
> expected.
> 
> Signed-off-by: Nicolas Pitre <nico@cam.org>


---
~Randy

  reply	other threads:[~2006-12-11  4:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09  8:36 [PATCH] ucb1400_ts depends SND_AC97_BUS Randy Dunlap
2006-12-10  2:50 ` Dmitry Torokhov
2006-12-10  2:57   ` Randy Dunlap
2006-12-10  3:05     ` Dmitry Torokhov
2006-12-10  3:17       ` Nicolas Pitre
2006-12-10  5:09         ` Randy Dunlap
2006-12-11  3:55           ` Nicolas Pitre
2006-12-11  4:45             ` Randy Dunlap [this message]
2008-09-05  2:57             ` Randy Dunlap
2008-09-05  4:37               ` Nicolas Pitre
2008-09-05  4:44                 ` Randy Dunlap
2008-09-05  5:09                   ` Nicolas Pitre
2008-09-05  6:46                     ` Takashi Iwai
2008-09-05 14:52                       ` Nicolas Pitre
2008-09-05 16:26                         ` Takashi Iwai
2008-09-05 16:32                           ` Nicolas Pitre
2008-09-05 17:17                             ` Takashi Iwai
2008-09-05 18:33                               ` Dmitry Torokhov
2008-09-06  9:54                                 ` Takashi Iwai
2008-09-05 21:09                               ` Randy Dunlap
2008-09-06  9:53                                 ` Takashi Iwai
2008-09-05  5:27                   ` Nicolas Pitre

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=20061210204545.a68d15cd.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@osdl.org \
    --cc=dtor@insightbb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    /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