Merge tag 'x86-misc-2024-05-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull tip tree documentation update from Ingo Molnar: - Update the -tip maintainers merge policy document wrt merge window timing * tag 'x86-misc-2024-05-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: Documentation/maintainer-tip: Clarify merge window policy
This commit is contained in:
@@ -409,20 +409,20 @@ See :ref:`resend_reminders`.
|
||||
Merge window
|
||||
^^^^^^^^^^^^
|
||||
|
||||
Please do not expect large patch series to be handled during the merge
|
||||
window or even during the week before. Such patches should be submitted in
|
||||
mergeable state *at* *least* a week before the merge window opens.
|
||||
Exceptions are made for bug fixes and *sometimes* for small standalone
|
||||
drivers for new hardware or minimally invasive patches for hardware
|
||||
enablement.
|
||||
Please do not expect patches to be reviewed or merged by tip
|
||||
maintainers around or during the merge window. The trees are closed
|
||||
to all but urgent fixes during this time. They reopen once the merge
|
||||
window closes and a new -rc1 kernel has been released.
|
||||
|
||||
Large series should be submitted in mergeable state *at* *least* a week
|
||||
before the merge window opens. Exceptions are made for bug fixes and
|
||||
*sometimes* for small standalone drivers for new hardware or minimally
|
||||
invasive patches for hardware enablement.
|
||||
|
||||
During the merge window, the maintainers instead focus on following the
|
||||
upstream changes, fixing merge window fallout, collecting bug fixes, and
|
||||
allowing themselves a breath. Please respect that.
|
||||
|
||||
The release candidate -rc1 is the starting point for new patches to be
|
||||
applied which are targeted for the next merge window.
|
||||
|
||||
So called _urgent_ branches will be merged into mainline during the
|
||||
stabilization phase of each release.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user