Lines Matching full:fixes
27 Generally speaking, fixes for the current cycle are applied directly to the
30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
51 Fixes that target the current release, a.k.a. mainline, are typically applied
61 close around rc5 for new features, and a soft close around rc6 for fixes (for
62 the next release; see above for fixes that target the current release).
67 room for the size of a series, patches that are "cache hot", etc. Fixes,
87 Fixes that target the current release, a.k.a. mainline, should be based on
88 ``git://git.kernel.org/pub/scm/virt/kvm/kvm.git master``. Note, fixes do not
90 rule, but typically only fixes for bugs that are urgent, critical, and/or were
226 Fixes section in Development
228 If a change fixes a KVM/kernel bug, add a Fixes: tag even if the change doesn't
229 need to be backported to stable kernels, and even if the change fixes a bug in
234 KVM x86 opts out of backporting Fixes: by default. Some auto-selected patches
294 Bug Fixes
296 Except for "obvious" found-by-inspection bugs, fixes must be accompanied by a
349 bug fixes, should be posted along with the KVM changes as a single series. The
352 tests that fail due to KVM bugs should be ordered after the KVM fixes.