On Thu, 9 Aug 2007 02:02:19 +0200 Michael Buesch <mb@xxxxxxxxx> 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. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
