Lines Matching full:about
23 expect to be told about problems, which most of the time will be by email with a
81 need special handling in some steps that are about to follow.
135 that hear about it for the first time. And if you learned something in this
136 process, consider searching again for existing reports about the issue.
144 * Start to compile the report by writing a detailed description about the
172 the point about regression within a stable or longterm kernel version line. You
179 line you care about: go to the `front page of kernel.org
308 developers in fact are willing to handle reports about issues occurring with
313 Sid or Fedora Rawhide. Some developers will also accept reports about issues
360 In case you find an existing report about your issue, join the discussion, as
382 need special handling in some steps that are about to follow.*
393 detail. It also provides a good deal of other information about regressions you
452 system. That's what you are about to do in this process. Thus, make sure to
584 people. The developers thus want to learn about such issues as quickly as
602 knowledge about the internals of remote or unrelated "subsystems", like the TCP
606 file your issue and make it reach the developers that need to know about it.
729 modified during tree-wide cleanups by developers that do not care about the
815 In about two out of every nine to ten weeks, mainline might point you to a
882 about it: they are as reliable as a proper pre-release, unless the kernel's
937 head over to the section "Details about reporting issues only occurring in
947 that hear about it for the first time. And if you learned something in this
948 process, consider searching again for existing reports about the issue.*
955 In this in the previous steps you likely have learned a thing or two about the
966 When the kernel detects an internal problem, it will log some information about
1010 be required to retrieve the relevant details. Don't worry about that, if that's
1032 will often require you to build about ten to twenty kernel images, trying to
1039 reports about it, if there are any.
1064 provides a good deal of other information about regressions you might want to be
1071 *Start to compile the report by writing a detailed description about the
1196 Don't worry too much about forgetting something, as developers will ask for
1209 crucial parts readers need to know to understand what this is all about; if you
1213 summary that explains quickly what the report is about. After that you have to
1263 offer a way to keep reports private, forget about it and send your report as
1303 reply there and do not contact any of the developers privately about it. For
1330 about it to a chatroom or forum you normally hang out.
1362 issue persists and makes sure they do not forget about it. A few other
1461 bit about programming and might be able to write a fix.
1474 line you care about: go to the front page of kernel.org and make sure it
1478 Most kernel version lines only get supported for about three months, as
1485 should consider switching to the newer one and forget about the older one:
1496 Maybe the issue you face is already known and was fixed or is about to. Hence,
1498 <https://lore.kernel.org/stable/>`_ for reports about an issue like yours. If
1589 version line your care about. In that case you'll have no other choice then to
1603 you care about.
1643 again for discussions about the issue. Search the net with your favorite
1654 backported to the version line you care about. If that's the case you have
1730 But don't worry too much about all of this, a lot of drivers have active