Kees Cook <keescook@xxxxxxxxxxxx> writes: >> >> > I was just walking through our patch tracker and noticed that I don't >> >> > see this patch include in -next yet (as of next-20240429). Is there a >> >> > flush of the ath-next queue planned soon? Or did I miss some change? >> >> >> >> Yeah, wireless-next was pulled last week so most likely we will create >> >> ath-next pull request this week. >> >> >> >> BTW we are planning to move ath.git to a new location, rename branches >> >> etc. I think we'll see if we can also setup it so that it can be pulled >> >> to linux-next, so that you don't need to ask this every time ;) >> >> >> >> (Just joking of course, there a lot of benefits from having the tree in >> >> linux-next) >> > >> > Ah-ha! Thanks. Yeah, sorry if I keep asking about that. It's different >> > from other trees, so it doesn't stick in my head. :) I should keep >> > better notes! >> >> BTW I think all vendor specific wireless driver trees are not pulled to >> linux-next: iwlwifi, mt76, rtw (Realtek) and ath. So with all of these it will >> take a while before the commit is in linux-next. > > How long is "a while"? The cadence can be anything from 1-4 times per release (~8 weeks). Depends on the maintainer, how busy we are etc. > And if the latency can be reduced for these, it'd be nice since it > would allow for longer bake-time in -next. Sure but our time is limited, as always :) There's extra overhead with linux-next, like the rule that no updates during the merge window, so I can understand why some maintainers have not included their tree to linux-next builds. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
