Lines Matching refs:to

10 backported to it.
14 Alternatively, you can attempt to run one of the supported stable or -rc
16 to reproduce the bug on the latest -rc kernel.
19 How to report Linux kernel bugs
27 increases your chances of getting your bug fixed. Simply posting to the
28 generic linux-kernel mailing list (LKML) may cause your bug report to be
31 Instead, try to figure out which kernel subsystem is causing the issue,
33 maintainer doesn't answer, then expand your scope to mailing lists like
37 Identify who to notify
41 bug report.  Some maintainers prefer bugs to be reported via bugzilla
45 To find out where to send an emailed bug report, find your subsystem or
47 entries, and send your bug report to the person(s) listed in the "M:"
48 lines, making sure to Cc the mailing list(s) in the "L:" lines.  When the
49 maintainer replies to you, make sure to 'Reply-all' in order to keep the
53 files to the get_maintainer.pl script:
61 a bug in kernel.org bugzilla and send email to
75 It's REALLY important to report bugs that seem unrelated as separate email
77 bugs at once, it's difficult for maintainers to tease apart the relevant
84 The most important information in a bug report is how to reproduce the
92 to make it useful to the recipient.
95 Having a standardized bug report form makes it easier for you not to
96 overlook things, and easier for the developers to find the pieces of
98 relevant to your bug, feel free to exclude it.
104 Use that information to fill in all fields of the bug report form, and
105 post it to the mailing list with a subject of "PROBLEM: <one line
126 [8.7.] Other information that might be relevant to the problem
128        think to be relevant):
138 Linux kernel maintainers expect bug reporters to be able to follow up on
141 frustrating thing for maintainers is for someone to report a bug, and then
142 never follow up on a request to try out a fix.
144 That said, it's still useful for a kernel maintainer to know a bug exists
146 up reports, such as replying to the email thread with "I tried the latest
148 maintainers have to assume silence means things are still broken.
154 they may not be able to address your bug in a day, a week, or two weeks.
159 In general, kernel maintainers take 1 to 5 business days to respond to
160 bugs.  The majority of kernel maintainers are employed to work on the
166 The exceptions to this rule are regressions, kernel crashes, security holes,
169 responding to these types of bugs in a timely manner (especially during a
170 merge window), escalate the bug to LKML and Linus Torvalds.