Documentation/admin-guide/reporting-issues.rst

12 longterm series? One still supported? Then search the `LKML
25 search the `LKML <https://lore.kernel.org/lkml/>`_ and the web, too. If you
31 If it shows the problem, search for the change that fixed it in mainline and
74  * Perform a rough search for existing reports with your favorite internet
75    search engine; additionally, check the archives of the `Linux Kernel Mailing
221    search the appropriate mailing lists for posts that discuss such an issue
331    *Perform a rough search for existing reports with your favorite internet
332    search engine; additionally, check the archives of the Linux Kernel Mailing
339 step of the process it's okay to just perform a rough search: a later step will
340 tell you to perform a more detailed search once you know where your issue needs
344 Simply search the internet with your favorite search engine first. Afterwards,
345 search the `Linux Kernel Mailing List (LKML) archives
348 If you get flooded with results consider telling your search engine to limit
349 search timeframe to the past month or year. And wherever you search, make sure
350 to use good search terms; vary them a few times, too. While doing so try to
352 come up with other words to use as search terms. Also make sure not to use too
353 many search terms at once. Remember to search with and without information like
356 often is not much helpful, as it is too specific. Instead try search terms like
500 the top of the error messages printed when one of these occurs and search for a
645 In case tricks like these don't bring you any further, try to search the
650 Once you know the driver or subsystem, you want to search for it in the
652 name is too specific. Sometimes you will need to search on the net for help;
742 as the reporter. That's why you should search for existing report again, now
753 quite a few other lists miss a way to search the archives. In those cases use a
754 regular internet search engine and add something like
755 'site:lists.infradead.org/pipermail/ath10k/' to your search terms, which limits
763 For details how to search and what to do if you find matching reports see
956 issue you face. Use this knowledge and search again for existing reports
1035 Thanks to a 'binary search' this will lead you to the one commit in the source
1036 code management system that's causing the regression. Once you find it, search
1380 many reasons why it's wise to quickly run an internet search to see who you're
1497 `search the archives of the Linux stable mailing list
1610 Check code history and search for existing discussions
1616     search the appropriate mailing lists for posts that discuss such an issue
1623 to get the issue solved. That's why you want to search for it or any
1630    a local clone you alternatively can search on the command line with ``git
1644    internet search engine as well as the archives for the `Linux kernel
1650  * If you see a proposed fix, search for it in the version control system as