Lines Matching full:reports

23 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
33 mailing list in CC. Check the destination's archives for matching reports;
83  * Perform a rough search for existing reports with your favorite internet
85    List (LKML) <https://lore.kernel.org/lkml/>`_. If you find matching reports,
115    Find out how and where its developers expect reports. Note: most of the
120    thoroughly for reports that might match your issue. If you find anything,
145    process, consider searching again for existing reports about the issue.
193    <https://lore.kernel.org/stable/>`_ for existing reports.
294 with reports for issues that don't even happen with their current code. It's
317 developers in fact are willing to handle reports about issues occurring with
322 Sid or Fedora Rawhide. Some developers will also accept reports about issues
333 better than not reporting the issue at all: sometimes such reports directly or
337 Search for existing reports, first run
340    *Perform a rough search for existing reports with your favorite internet
342    List (LKML). If you find matching reports, join the discussion instead of
378 reports. If you find the latter, just keep in mind: most subsystems expect
379 reports in different places, as described below in the section "Check where you
512 why the kernel also mentions the taint status when it reports an internal
609     Find out how and where its developers expect reports. Note: most of the
703 issue reports sent by email, make sure to add the Linux Kernel Mailing List
707 and LKML is important to have one place where all issue reports can be found.
748 Search for existing reports, second run
752     thoroughly for reports that might match your issue. If you find anything,
778 For details how to search and what to do if you find matching reports see
779 "Search for existing reports, first run" above.
799 reports for issues that don't even happen with the current code. It's just a
837 quite busy then and might have no spare time to deal with issue reports. It's
963     process, consider searching again for existing reports about the issue.*
971 issue you face. Use this knowledge and search again for existing reports
1054 reports about it, if there are any.
1242 Reports for high priority issues need special handling.
1277    offer a way to keep reports private, forget about it and send your report as
1318 mailed reports always use the 'Reply-all' function when replying to any mails
1352 reports. Sometimes it will take longer, as they might be busy with the merge
1417 Some reports will not get any reaction from the responsible Linux kernel
1508     *Check the archives of the Linux stable mailing list for existing reports.*
1512 <https://lore.kernel.org/stable/>`_ for reports about an issue like yours. If
1619  * Search the Linux stable mailing list for exiting reports.
1740 get overwhelmed with reports, even if a driver is working nearly perfectly. To
1742 to prioritize issue reports and reject some of them.