Documentation/admin-guide/reporting-issues.rst

22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers
51 Step-by-step guide how to report issues to the kernel maintainers
155    ready to send or file the report like the MAINTAINERS file told you, unless
227    out, ask the maintainers for the subsystem that seems to be causing the
234 Reference section: Reporting issues to the kernel maintainers
609 kernel developers and experts. For everybody else the MAINTAINERS file is the
612 How to read the MAINTAINERS file
614 To illustrate how to use the :ref:`MAINTAINERS <maintainers>` file, lets assume
651 MAINTAINERS file. In the case of 'ath10k_pci' you won't find anything, as the
654 MAINTAINERS file, as then you might find something like this::
665 MAINTAINERS file found in the root of the Linux source tree. 'Mail:' for
685 maintainers of the particular code. Also look for a line starting with 'Mailing
690 lists when sending your issue report by mail later! Maintainers are busy people
695 Finding the maintainers with the help of a script
700 to find all people to contact. It queries the MAINTAINERS file and needs to be
717 Don't sent your report to all of them. Send it to the maintainers, which the
1027 down the culprit, as maintainers often won't have the time or setup at hand to
1082     ready to send or file the report like the MAINTAINERS file told you, unless
1220 Now send or file the report like the :ref:`MAINTAINERS <maintainers>` file told
1258  * If the MAINTAINERS file instructed you to report the issue by mail, do not
1264    a private mail to the maintainers instead.
1267 MAINTAINERS file lists in the section 'security contact'. Ideally directly CC
1333 within a few hours. But most of the time it will take longer, as maintainers
1343 here: maintainers should address them as soon as possible; that's why you
1352 driver that would be the wireless maintainers; if there are no higher level
1353 maintainers or all else fails, it might be one of those rare situations where
1436 contact a higher-level maintainer asking for advice: even busy maintainers by
1439 Remember to prepare yourself for a disappointment: maintainers ideally should
1541 the cause in a particular subsystem, CC its maintainers and its mailing list
1581 totally unexpected problems. The maintainers of the stable and longterm kernels
1667     out, ask the maintainers for the subsystem that seems to be causing the
1672 one option left: ask for advice. Do that in a mail you sent to the maintainers
1682 to get resolved. The maintainers or if all else fails Linus Torvalds himself
1722 Priorities are another reason why some issues are not fixed, as maintainers
1725 spend on maintenance work on the upstream kernel. Sometimes maintainers also
1731 maintainers who are quite interested in fixing as many issues as possible.