On Thu, Nov 29, 2012 at 11:29:55AM +0200, Vladimir Kondratiev wrote: > Hi, > > I have the following situation: > > - there is the driver for 60g WiFi card, "wil6210", that I want to merge. It > consists of 2 patches: > > wireless: Driver for 60GHz card wil6210 > wireless: integrate wil6210 driver into build > > - then, there is one more patch for Atheros drivers family config that I rely > on: > > wireless: allow Atheros card to not depend on ath.ko > > - and, there is one more patch that I depend on: > > dynamic_debug: dynamic hex dump > > Discussion about last patch was taken from linux-wireless to the LKML, and it > get pushed to Greg K-H by Jason Baron. > > So, question is: what is the right strategy for wil6210 driver? > > Shall I wait till 2 patches I depend on get merged? Some other idea? > > Please advise. > > Thanks, Vladimir Since Greg is merging one patch and I'm merging the other, under normal circumstances they will only reach the same tree sometime during the 3.8 merge window. FWIW, I was under the impression that you were targeting 3.9 anyway. If so, you can simply wait to have your driver merged sometime after 3.8-rc1. Does that help? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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