Messages in this thread | | | Date | Thu, 8 Nov 2018 08:46:45 +0100 | From | Ingo Molnar <> | Subject | Re: [patch 2/2] Documentation/process: Add tip tree handbook |
| |
Lemme fill in the scheduler and locking/atomics bits as well:
> +The tip tree contains the following subsystems: > + > + - **x86 architecture** > + > + The x86 architecture development takes place in the tip tree except > + for the x86 KVM and XEN specific parts which are maintained in the > + corresponding subsystems and routed directly to mainline from > + there. It's still good practice to Cc the x86 maintainers on > + x86-specific KVM and XEN patches. > + > + Some x86 subsystems have their own maintainers in addition to the > + overall x86 maintainers. Please Cc the overall x86 maintainers on > + patches touching files in arch/x86 even when they are not called out > + by the MAINTAINER file. > + > + Note, that ``x86@kernel.org`` is not a mailing list. It is merely a > + mail alias which distributes mails to the x86 top-level maintainer > + team. Please always Cc the Linux Kernel mailing list (LKML) > + ``linux-kernel@vger.kernel.org``, otherwise your mail ends up only in > + the private inboxes of the maintainers. > + > + - **Scheduler**
Scheduler development takes place in the -tip tree, in the sched/core branch - with occasional sub-topic trees for work-in-progress patch-sets.
> + > + - **Locking and atomics**
Locking development (including atomics and other synchronization primitives that are connected to locking) takes place in the -tip tree, in the locking/core branch - with occasional sub-topic trees for work-in-progress patch-sets.
Thanks,
Ingo
| |