From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: jengelh@linux01.gwdg.de, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH 11/12] pcmcia/net_pcmcia: all net_pcmcia modules depend on PCMCIA
Date: Thu, 21 Jun 2007 19:06:17 +0200 [thread overview]
Message-ID: <20070621170617.GH5193@alberich.amd.com> (raw)
In-Reply-To: <20070620134435.21410ceb.randy.dunlap@oracle.com>
On Wed, Jun 20, 2007 at 01:44:35PM -0700, Randy Dunlap wrote:
> On Wed, 20 Jun 2007 00:52:03 +0200 Andreas Herrmann wrote:
>
> > Fix several build errors with PCMCIA=m && NET_PCMCIA=y:
> >
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `nmclan_release':
> > nmclan_cs.c:(.text+0x14026c): undefined reference to `pcmcia_disable_device'
> > ...
> > drivers/built-in.o: In function `exit_xirc2ps_cs':
> > xirc2ps_cs.c:(.exit.text+0x1055): undefined reference to `pcmcia_unregister_driver'
> > make: *** [.tmp_vmlinux1] Error 1
>
> This is interesting. This is a result of the menuconfig changes,
> which made NET_PCMCIA a boolean, and then some tristates depend
> on NET_PCMCIA and the boolean -> tristate dependencies aren't
> specific enough.
>
> Your fix is one way to do it. I'd prefer to make
> NET_PCMCIA a tristate instead, then let its value trickle down
> to the subordinate config symbols.
>
> This probably means that some of the other menuconfig changes
> need to be audited for this "feature."
>
>
> Here is my preferred patch.
> ~~~~~~~~~~
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Make NET_PCMCIA a tristate symbol so that net/pcmcia drivers
> are constrained to M when needed.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> drivers/net/pcmcia/Kconfig | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> --- linux-2.6.22-rc5.orig/drivers/net/pcmcia/Kconfig
> +++ linux-2.6.22-rc5/drivers/net/pcmcia/Kconfig
> @@ -3,14 +3,14 @@
> #
>
> menuconfig NET_PCMCIA
> - bool "PCMCIA network device support"
> + tristate "PCMCIA network device support"
> depends on PCMCIA
Yes this solves the problem.
... and is the preferred variant.
Regards,
Andreas
--
Operating | AMD Saxony Limited Liability Company & Co. KG,
System | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Research | Register Court Dresden: HRA 4896, General Partner authorized
Center | to represent: AMD Saxony LLC (Wilmington, Delaware, US)
(OSRC) | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
prev parent reply other threads:[~2007-06-21 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 22:52 [PATCH 11/12] pcmcia/net_pcmcia: all net_pcmcia modules depend on PCMCIA Andreas Herrmann
2007-06-20 20:44 ` Randy Dunlap
2007-06-20 21:25 ` Satyam Sharma
2007-06-20 22:34 ` Randy Dunlap
2007-06-21 17:06 ` Andreas Herrmann [this message]
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=20070621170617.GH5193@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=randy.dunlap@oracle.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