|firstname.lastname@example.org||(LKML) Linux Kernel Development: technical discussions related to upstream and RT tree patches with all developers and maintainers.||LKML FAQ||The Aims Group|
|email@example.com||Real-Time Linux Users: Release announcements, bug reports and handling, general usage questions, development or user-space tools (e.g. rt-test suite)||MajorDomo||GMANE, spinics.net|
|firstname.lastname@example.org||glibc open development list||Sourceware||RedHat|
Note the subtle difference in description of linux-kernel and linux-rt-users lists above. The linux-rt-users list is intended for users who want to ask questions about using the -rt patch set. Kernel-related development issues about the real-time patchsets should be sent to the linux-kernel.
Thomas Gleixner wrote regarding this:
All patches against the RT tree should be posted to LKML. CCing rt-users is fine, but development needs to happen on the main kernel development list because only a few developers/maintainers are subscribed to rt-users.
Theodore Tso wrote regarding this:
One of the reasons why we (in consultation with folks like Ingo and tglx) deliberatly didn't create a RT development list was that in order to promote getting -rt related patches into mainline as soon as possible, we wanted to keep patch and development discussion on LKML. For example, it's not clear that the ARM maintainer subscribes to linux-rt-users; furthermore the more patch discussion happens on LKML, it helps promote willingness of other kernel developers that CONFIG_PREEMPT_RT isn't going to go away, and will probably (hopefully!) be merged into mainline someday soon.