From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.21-mm1
Date: Sat, 5 May 2007 18:25:01 -0400 [thread overview]
Message-ID: <20070505222501.GD23938@tuxdriver.com> (raw)
In-Reply-To: <200705052348.49994.mb@bu3sch.de>
On Sat, May 05, 2007 at 11:48:49PM +0200, Michael Buesch wrote:
> On Saturday 05 May 2007 20:48:11 Andrew Morton wrote:
> > On Sat, 05 May 2007 17:48:28 +0200 Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
> >
> > > Andrew Morton pisze:
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/
> > > >
> > > >
> > >
> > > CC [M] lib/zlib_deflate/deflate_syms.o
> > > LD [M] lib/zlib_deflate/zlib_deflate.o
> > > Building modules, stage 2.
> > > MODPOST 791 modules
> > > ERROR: "ssb_pcihost_register" [drivers/net/b44.ko] undefined!
> > > ERROR: "ssb_pcihost_unregister" [drivers/net/b44.ko] undefined!
> > > make[2]: *** [__modpost] Error 1
> > > make[1]: *** [modules] Error 2
> > > make[1]: Leaving directory `/usr/src/linux-mm'
> > > make: *** [debian/stamp-build-kernel] Error 2
>
> config B44_PCI
> bool "Broadcom 4400 PCI device support"
> depends on B44 && NET_PCI
>
> We simply need a SELECT SSB_PCIHOST here. Not sure why it's not there.
> I thought it used to be there.
That may have only been applied to the mm-master branch, which now
no longer exists. I'll patch it now.
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-05-05 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070505014955.8f3990b5.akpm@linux-foundation.org>
[not found] ` <463CA74C.8080008@gmail.com>
2007-05-05 18:48 ` 2.6.21-mm1 Andrew Morton
2007-05-05 21:48 ` 2.6.21-mm1 Michael Buesch
2007-05-05 22:25 ` John W. Linville [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=20070505222501.GD23938@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mb@bu3sch.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;
as well as URLs for NNTP newsgroup(s).