Johannes Berg wrote:
On Tue, 2007-07-10 at 16:29 +0200, Jiri Benc wrote:
But even if it can be applied upstream, it doesn't solve anything. Imagine
a patch which was merged into wireless-dev before this restructuring and
which is not upstream. Merging it upstream would mean taking the patch from
wireless-dev git and manually modifying it to fit a new structure. And we
have a bunch of such patches which should go to 2.6.24 (yes, I really
mean .24). Perhaps I'm lazy, but I'd like to avoid that. It's going to be a
lot of unpleasant work even without this...
Which all goes to say that pushing mac80211 for .22 was too fast.
Definitely not too fast.
The fact that people are using mac80211 from Linus' kernel tip is *GREAT*.
We have a lot of users now that can pull Linus' tree and use iwlwifi and
they no longer have to figure out how to patch a kernel, or pull from
wireless-dev.
The fact that people are working on making patches against mac80211 is
exactly what mac80211 needs. By pushing at least some bits out we now
have a larger audience testing, contributing, and working on making
mac80211 better.
James
-
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
