Kalle,
I was answering a query regarding the driver for RTW8852BE, and happened to
check the configuration for 6.1-rc and discovered that the appropriate Kconfig
and Makefile are missing the following:
commit b5db4ef38e21dd9b6b95ae96cea5032b00e04f24
Author: Ping-Ke Shih <[email protected]>
Date: Fri Oct 14 14:02:37 2022 +0800
wifi: rtw89: 8852b: add 8852be to Makefile and Kconfig
I expected that this one would have been sent upstream to mainline by now. Is my
expectation wrong, or is the commit missing?
Larry
Hi Larry,
Larry Finger <[email protected]> writes:
> I was answering a query regarding the driver for RTW8852BE, and
> happened to check the configuration for 6.1-rc and discovered that the
> appropriate Kconfig and Makefile are missing the following:
>
> commit b5db4ef38e21dd9b6b95ae96cea5032b00e04f24
> Author: Ping-Ke Shih <[email protected]>
> Date: Fri Oct 14 14:02:37 2022 +0800
>
> wifi: rtw89: 8852b: add 8852be to Makefile and Kconfig
>
> I expected that this one would have been sent upstream to mainline by
> now. Is my expectation wrong, or is the commit missing?
That commit is in wireless-next and the first release having it should
be v6.2-rc1, if all goes well. So the patch is not lost.
We need to get -next patches ready before the merge window opens, so it
takes quite some time before patches go to an actual release. For
example, the estimation for the v6.2 merge window to start is on
2022-12-11. This means that wireless patches should be submitted by
latest 2022-12-05 to make the deadline, and even that's risky. The
estimation for the final v6.2 release is 2023-02-19:
https://phb-crystal-ball.sipsolutions.net/
So we can easily talk about 3-10 weeks delays before a -next patch is in
an -rc release, depending on what part of the release cycle we are.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
On 11/20/22 15:12, Kalle Valo wrote:
> That commit is in wireless-next and the first release having it should
> be v6.2-rc1, if all goes well. So the patch is not lost.
>
> We need to get -next patches ready before the merge window opens, so it
> takes quite some time before patches go to an actual release. For
> example, the estimation for the v6.2 merge window to start is on
> 2022-12-11. This means that wireless patches should be submitted by
> latest 2022-12-05 to make the deadline, and even that's risky. The
> estimation for the final v6.2 release is 2023-02-19:
Kalle,
Thanks for the explanation. Things always take longer than expected.
Larry