public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski•net>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-kbuild@vger•kernel.org, linux-next@vger•kernel.org,
	LKML <linux-kernel@vger•kernel.org>,
	Valdis.Kletnieks@vt•edu
Subject: Re: linux-next: Tree for January 7 (pcmcia)
Date: Thu, 7 Jan 2010 21:57:28 +0100	[thread overview]
Message-ID: <20100107205728.GA19115@isilmar.linta.de> (raw)
In-Reply-To: <20100107101006.e59989a8.rdunlap@xenotime.net>

Hey,

On Thu, Jan 07, 2010 at 10:10:06AM -0800, Randy Dunlap wrote:
> > Hi all,
> > 
> > Changes since 20100106:
> 
> 
> drivers/built-in.o: In function `yenta_probe':
> yenta_socket.c:(.devinit.text+0x1e582): undefined reference to `pccard_nonstatic_ops'
> 
> CONFIG_PCCARD=y
> CONFIG_PCMCIA=m
> CONFIG_PCCARD_NONSTATIC=m
> CONFIG_YENTA=y
> 
> so yenta code (built-in) tries to reference data that lives in a
> loadable module.

Uh, that was I. If kconfig can't be fixed easily, I'll revert the change

>  But I would expect this Kconfig:
> 
> config YENTA
> 	tristate "CardBus yenta-compatible bridge support"
> 	depends on PCI
> 	select CARDBUS if !EMBEDDED
> 	select PCCARD_NONSTATIC if PCMCIA
> 
> to make PCCARD_NONSTATIC=y instead of =m.  Has something changed in
> kconfig recently that would make that different?

Best,
	Dominik

  reply	other threads:[~2010-01-07 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  6:21 linux-next: Tree for January 7 Stephen Rothwell
2010-01-07 18:10 ` linux-next: Tree for January 7 (pcmcia) Randy Dunlap
2010-01-07 20:57   ` Dominik Brodowski [this message]
2010-01-07 21:07     ` Michal Marek
2010-01-07 21:55       ` Randy Dunlap
2010-01-08 17:54         ` Dominik Brodowski
2010-01-08 19:24           ` Michal Marek

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=20100107205728.GA19115@isilmar.linta.de \
    --to=linux@dominikbrodowski$(echo .)net \
    --cc=Valdis.Kletnieks@vt$(echo .)edu \
    --cc=linux-kbuild@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@xenotime$(echo .)net \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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