1
compat-wireless pending-stable/ patches
2
=======================================
4
Often right before the merge window we get a block on non
5
oops/regression fixes for stable fixes. Some stable fixes
6
often get propagated afterwards during the extraversion
7
maintenance of the kernels. Right before the merge window
8
circa rc4 and rc5 subsystem maintainers get pegged if they
9
throw in non oops/regression fixes for Linus or their
10
respective upstream maintainer. While this makes sense
11
for tree management and stable release considerations we
12
still need to get users some stable patches propagated.
14
This directory is there to help with that. Only patches
15
which have been merged into linux-next.git will be included
16
in this directory which means you must post it and the maintainer
17
should have merged it and Stephen would have picked it up.
19
This directory will always be empty for bleeding edge
20
releases as bleeding edge releases are always based on
21
linux-next already. This directory only makes sense for
22
stable release of the kernel, and it we will always try
23
to use it, in case there are stable fixes not yet propagated.