From: Andrew Morton <akpm@linux-foundation.org>
To: Aurelien Jarno <aurelien@aurel32.net>,
Michael Buesch <mb@bu3sch.de>,
John Linville <linville@tuxdriver.com>,
Felix Fietkau <nbd@openwrt.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ssb: Make extif driver compilation depend on extif config
Date: Wed, 8 Aug 2007 16:58:21 -0700 [thread overview]
Message-ID: <20070808165821.c2a6f290.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070808164327.45803a64.akpm@linux-foundation.org>
On Wed, 8 Aug 2007 16:43:27 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> I'm hopelessly confused by the ssb stuff. I'm not sure if I have all the
> right stuff, all the latest stuff and I don't understand why some is going
> into git-wireless and some is not.
So I dropped the duplicated patch, then a few other things which appeared to depend
on it and now...
drivers/ssb/main.c: In function 'ssb_clockspeed':
drivers/ssb/main.c:823: error: implicit declaration of function 'ssb_extif_get_clockcontrol'
So I shall now drop use-ssb-extif-in-ssb-mips-core-driver.patch
But the confidence level is really low. Michael, I think it's time to
do a reset, drop everything and start again. I trust you have a copy
of everything. You'll be cc'ed as they drop..
next prev parent reply other threads:[~2007-08-08 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 15:44 [PATCH] ssb: Make extif driver compilation depend on extif config Michael Buesch
2007-08-08 22:48 ` Andrew Morton
2007-08-08 23:13 ` Aurelien Jarno
2007-08-08 23:43 ` Andrew Morton
2007-08-08 23:58 ` Andrew Morton [this message]
2007-08-09 0:02 ` Michael Buesch
2007-08-09 0:10 ` Andrew Morton
2007-08-09 0:20 ` Michael Buesch
2007-08-09 0:28 ` Andrew Morton
2007-08-09 9:54 ` Michael Buesch
2007-08-09 9:44 ` Aurelien Jarno
2007-08-09 0:13 ` Andrew Morton
2007-08-09 14:01 ` John W. Linville
2007-08-09 14:38 ` Michael Buesch
2007-08-09 13:53 ` John W. Linville
2007-08-09 14:08 ` Michael Buesch
2007-08-09 14:23 ` John W. Linville
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=20070808165821.c2a6f290.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aurelien@aurel32.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).