=====Mailing lists=====

^ List ^ Description ^
|**linux-rt-users@vger.kernel.org** | Real-Time Linux Users: Release announcements, bug reports and handling, general usage questions, development or user-space tools (e.g. rt-test suite).  [[majordomo@vger.kernel.org?body=subscribe%20linux-rt-users | subscribe linux-rt-users]]  [[majordomo@vger.kernel.org?body=unsubscribe%20linux-rt-users | unsubscribe linux-rt-users]] |
|**linux-kernel@vger.kernel.org** | (LKML) Linux Kernel Development: technical discussions related to upstream and RT tree patches with all developers and maintainers. [[majordomo@vger.kernel.org?body=subscribe%20linux-kernel | subscribe linux-kernel]] [[majordomo@vger.kernel.org?body=unsubscribe%20linux-kernel | unsubscribe linux-kernel]] |

Information about all Linux kernel developer mailing lists is provided on [[http://vger.kernel.org|vger.kernel.org]]. If there are questions about LKML, please consider [[http://www.tux.org/lkml/|LKML FAQs]] first.

<WRAP left round important>

All patches against the RT tree should be [[realtime:communication:send_rt_patches | 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. Furthermore, the
more patch discussion happens on LKML, the more it helps promote the
willingness of other kernel developers to accept that
CONFIG_PREEMPT_RT isn't going to go away, and will probably
(hopefully!) be merged into mainline someday soon.

The linux-rt-users list is intended for users who want to ask questions about using the -rt patch set.
</WRAP>


If you are interested in sending patches for improvements or bug fixes for RT, please see [[realtime:communication:send_rt_patches | Send Patches for RT]].