Documentation/admin-guide/reporting-issues.rst

47 Once the report is out, answer any questions that come up and help where you
59 out a lot of details; those are described below the step-by-step guide in a
106    Find out how and where its developers expect reports. Note: most of the
227    out, ask the maintainers for the subsystem that seems to be causing the
300 report and, in case it turns out to be an upstream issue, fix it directly
301 upstream or forward the report there. In practice that often does not work out
305 explain how to do that once it rules out other potential causes for your issue.
364 test a proposed fix. Jump to the section 'Duties after the report went out' for
417 runtime environment. It's hard to rule out that problem completely, but you
488 rule this out early before investing more time into this process. This is the
506 to find out why. Try to eliminate the reason. Often it's caused by one these
519     Rule this out by getting rid of the cause for the first Oops and reproducing
568 try to rule that out by reproducing the issue before going further. Feel free
594     Find out how and where its developers expect reports. Note: most of the
673 'Orphan' you are totally out of luck, as nobody takes care of the code anymore.
806 Head over to `kernel.org <https://kernel.org/>`_ to find out which version you
815 In about two out of every nine to ten weeks, mainline might point you to a
826 the report went out'.
1044 don't want to go down that route at least find out which mainline kernel
1152    went out. ;-)
1208 describes the issue roughly. Leave out all boring details and focus on the
1275 Duties after the report went out
1293 once you got the report out. What you'll have to do depends on the situations,
1330 about it to a chatroom or forum you normally hang out.
1383 later if discussion fades out without leading to a satisfying solution for the
1404 developers; or a discussion around the issue evolved, but faded out with
1405 nothing of substance coming out of it.
1411 get the ball running somehow. If the report got out by mail, do that in the
1420 to reach out to the wrong people? Was the report maybe offensive or so
1422 rule out such factors: show the report to one or two people familiar with FLOSS
1425 review it before you send it out. Such an approach is totally fine; just
1447 nothing happens anymore and reminders don't help to motivate anyone to work out
1518 vendor applied might be interfering. You need to rule that out by performing
1556 Once your report is out your might get asked to do a proper one, as it allows to
1599 You need to carry out a few steps already described in another section of this
1667     out, ask the maintainers for the subsystem that seems to be causing the