Johannes, We understand that these two issues need to be taken care of, and they will be. My concern is that if current patches won't be merged soon, we will have to pay the effort to rebase the patches again. We are very limited with resources dedicated to supporting the merge of 802.11n to wireless-dev. This mailing list taught us in the "hard way" in the recent months: submit often submit early... So for making Ron's work efficient I suggest to merge his patches and let him do the fixes on top of them, specially since the two fixes are not 802.11n core critical issues and don't break any existing working flows. Do you feel comfortable with this approach? Guy. On 11/14/07, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > Overall, looks pretty good. I personally prefer things like (!xyz) > rather than (xyz == NULL) but that's totally minor. I'll take a more > detailed look later and check out the frame flow etc. > > > - Changes to Rx handlers PAE and drop unencrypted (for EAPOL frames in amsdu) > > - Examine config flows in mac80211 (RFC is prepered) > > I'd prefer to have this patch series depend on these two items instead > because as it stands, we have a weird behaviour here and quite a lot of > duplicated code in the data/agg_data RX handlers. I thought your RFC was > pretty good except that you didn't want to convert existing stuff to it, > so... > > johannes > > - 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
