Re: Confused - bisecting wireless-testing

["John W. Linville" <linville@tuxdriver.com>]

On Tue, Jul 27, 2010 at 09:21:40AM -0700, Luis R. Rodriguez wrote:
> On Tue, Jul 27, 2010 at 9:04 AM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Tue, Jul 27, 2010 at 08:56:54AM -0700, Luis R. Rodriguez wrote:
> >> On Tue, Jul 27, 2010 at 7:01 AM, John W. Linville
> >> <linville@tuxdriver.com> wrote:

> >> > As for right now, it sounds like you should just use wireless-next-2.6
> >> > instead?
> >>
> >> Oh OK, didn't realize that was bisectable, thanks. Also was unsure if
> >> I'd get other subsystems's -next components. Is wireless-next.git just
> >> the -next bits for 802.11 or does it also suck up net-next?
> >
> > Usually just the wireless bits, but I did just pull the bluetooth stuff
> > (which included some net-next stuff).
> 
> Oh neat. OK so which net-next.git release was wireless-next.git based
> on and what net-next.git release was bluetooth-next.git based on? Did
> it bump your next-next.git or do you routinely pull next-next.git into
> your own wireless-next.git?

I don't have those exact commit IDs.  How badly do you need them?

I don't normally pull net-next into wireless-next, but this release
not doing that has been a source of pain due to the __packed patch
in net-next and the addition of __attribute__ ((packed)) in various
places in wireless-next.  Since Marcel had already based on a net-next
that had that patch and since it is close to the end of the release
I decided it would be acceptable to pull it this time.

I have been considering making regular net-next pulls a standard
practice.  That would make my life easier, but would add some
non-wireless instability into wireless-testing (which pulls from
wireless-next).  I don't think that would be a big problem _most_
of the time, but I'm sure there would be some occasional pain from
doing that.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.