From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
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 17:13:30 -0700 [thread overview]
Message-ID: <20070808171330.b374ec12.akpm@linux-foundation.org> (raw)
In-Reply-To: <200708090202.20267.mb@bu3sch.de>
On Thu, 9 Aug 2007 02:02:19 +0200
Michael Buesch <mb@bu3sch.de> 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.
>
> Everything is going into git-wireless.
> git-wireless contains latest ssb. _but_ John complained
> about that. And he is right. SSB is not strictly wireless core.
> So I thought it was best to get ssb into mainline as soon as
> possible. So -mm is really the way to go into mainline.
> My plan was to merge mainline with the next merge window.
>
> > I'd prefer to be dumbly pulling a tree which Michael controls rather than
> > trying to master it all in -mm, if possible. A git tree or a quilt tree in
> > some open dir somewhere would suit?
>
> It's a bit difficult, as bcm43xx depends on it. Which again depends
> on the wireless tree. :)
> So basically we are stuck with maintaining it in wireless-dev.
>
> I don't know what your policy is with pulling from wireless-dev.
> So wireless-dev currently contains latest SSB. So if you pull from
> wireless-dev, you'll also get latest SSB. Though, if we want to
> merge SSB soon, we need it broken-out. That is what I was trying
> to do.
Yeah, after dropping all the ssb stuff, my build is now busted because
the bit of git-wireless which I have wants SSB bits for BCM43XX.
argh. I'll try disabling b44 so I can get a release out the door.
Please, just give me some internally-consistent tree(s) to pull??
Thanks.
next prev parent reply other threads:[~2007-08-09 0:15 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
2007-08-09 0:13 ` Andrew Morton [this message]
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=20070808171330.b374ec12.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.