Lines Matching full:reporting

5 …rg/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-issues.rst
13 Reporting issues
65 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
79    document and reporting the issue to your vendor instead, unless you are
126    go and install it for the reporting process. Testing and reporting with
177 Reporting regressions within a stable and longterm kernel line
212 Reporting issues only occurring in older kernel version lines
243 Reference section: Reporting issues to the kernel maintainers
289    document and reporting the issue to your vendor instead, unless you are
303 Most of these vendor kernels are quite unsuitable for reporting issues to the
333 better than not reporting the issue at all: sometimes such reports directly or
345 Reporting an issue that someone else already brought forward is often a waste of
350 to be reported to. Nevertheless, do not hurry with this step of the reporting
395 handled slightly differently in the reporting process. Three type of cases
577 Additionally, during the reporting process you will have to test if the issue
755 As mentioned earlier already: reporting an issue that someone else already
781 Do not hurry with this step of the reporting process: spending 30 to 60 minutes
789     go and install it for the reporting process. Testing and reporting with
802 before reporting it. You are free to ignore this advice, but as outlined
832 suspending the reporting process until the first pre-release of the next
848 using it for reproducing the issue is also better than not reporting it issue
856 hard or risky for backporting; reporting the issue again hence is unlikely to
860 are unsuitable for this part of the reporting process: they are to distant from
872 unsuitable for testing and issue reporting: the changes might cause the issue
921 hard to reproduce. Sending an undecoded report is better than not reporting
935 eliminate the reason for it before you reporting issues that occur with it. See
952 head over to the section "Details about reporting issues only occurring in
1039 way. Reporting a regression is thus a bit like playing a kind of trump card to
1066 version which introduced the regression, feel free to move on in the reporting
1268 If that's not the case simply proceed with reporting the issue as described.
1269 For issues that bear such a risk you will need to adjust the reporting process
1437 issue reporting and ask for their opinion. Also ask them for their advice how
1478 Reference for "Reporting regressions within a stable and longterm kernel line"
1503 reporting.
1551 When reporting a regression that happens within a stable or longterm kernel
1580 Reference for "Reporting issues only occurring in older kernel version lines"
1610     *Perform the first three steps in the section "Reporting issues only
1694 When reporting a problem to the Linux developers, be aware only 'issues of high