From: Aurelien Jarno <aurelien@aurel32.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Thu, 09 Aug 2007 11:44:01 +0200 [thread overview]
Message-ID: <46BAE1E1.9000804@aurel32.net> (raw)
In-Reply-To: <200708090220.32981.mb@bu3sch.de>
Michael Buesch a =E9crit :
> On Thursday 09 August 2007, Andrew Morton wrote:
>> Still confused.
>>
>> I pull
>> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/linville/wirele=
ss-dev.git#mm-master
>> into -mm. Could be that John puts other things into other trees whi=
ch do
>> not appear in #mm-master, I don't know.
>>
>> Given that you are the developer and maintainer of ssb it is appropr=
iate
>> (especially at this stage) that you run a tree. Just a plain old qu=
ilt
>> tree like
>> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/greg=
kh-01-driver/
>> would be fine.
>>
>> If that tree is relative to some tree which John is running then tha=
t's OK,
>> as long as someone tells me where to get that tree from.
>>
>> Or just merge all of SSB via John's tree. I don't think it matters =
that
>> it's not strictly a wireless thing. =20
>=20
> I can live with doing it through John.
> And as bcm43xx depends on ssb we are doomed to go through
> John's tree.
> So if you always pull John's tree, you'll be up to date with
> wireless + ssb.
>=20
> So if you drop everything b44, bcm43xx and ssb related
> and pull John's tree, it will compile again.
I have compared the branches master and mm-master in John's tree. Only
drivers/ssb/driver_extif.c is present in mm-master, other files from th=
e
same directory and files from include/linux/ssb/* are missing. Also the
changes to drivers/Kconfig and drivers/Makefile are also missing in
mm-master.
So in short there is only one file concerning SSB drivers in the
mm-master branch and it is useless without the other files.
On the other side b44 and bcm43xx drivers that use the SSB drivers are
present in the mm-master branch.
--=20
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-08-09 9:44 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
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 [this message]
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=46BAE1E1.9000804@aurel32.net \
--to=aurelien@aurel32.net \
--cc=akpm@linux-foundation.org \
--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).