From: Michael Buesch <mb@bu3sch.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: linux-next: Tree for March 2 (wireless/b43)
Date: Mon, 2 Mar 2009 18:17:12 +0100 [thread overview]
Message-ID: <200903021817.12441.mb@bu3sch.de> (raw)
In-Reply-To: <49AC0FAB.6000604@oracle.com>
On Monday 02 March 2009 17:56:11 Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20090227:
> >
> > Undropped trees:
> > wireless
>
> when CONFIG_SSB_DRIVER_PCICORE=n:
>
> if ((bus->bustype == SSB_BUSTYPE_PCI) &&
> (bus->pcicore.dev->id.revision <= 10))
> hf |= B43_HF_PCISCW; /* PCI slow clock workaround. */
>
> ==>
> drivers/net/wireless/b43/main.c:4182: error: 'struct ssb_pcicore' has no member named 'dev'
>
>
>
>
I'll send a fix asap.
--
Greetings, Michael.
prev parent reply other threads:[~2009-03-02 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090302182217.90ca3356.sfr@canb.auug.org.au>
2009-03-02 16:56 ` linux-next: Tree for March 2 (wireless/b43) Randy Dunlap
2009-03-02 17:17 ` Michael Buesch [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=200903021817.12441.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).