Lines Matching full:those
42 those who handled the change for it.
68 out a lot of details; those are described below the step-by-step guide in a
89 issue, or a really severe problem: those are 'issues of high priority' that
165 you are dealing with one of those 'issues of high priority': they need
182 face one of those if something breaks when updating from 5.10.4 to 5.10.5 (a
218 kernels regularly rebased on those. If that the case, follow these steps:
248 experienced users might wonder how to actually do one of those steps. That's
252 details how to actually perform those steps.
332 those often get rejected or ignored, so consider yourself warned. But it's still
390 issue, or a really severe problem: those are 'issues of high priority' that
482 mechanisms like akmods and DKMS: those build add-on kernel modules
546 prevent those modules from loading when you want to report an issue to the
652 other internal bus. In those cases you might want to check your WiFi manager or
696 a bug tracker, and only some of those rely on bugzilla.kernel.org.
699 'Mail:' instead. Those mention the name and the email addresses for the
702 Your report later needs to go by mail to those addresses. Additionally, for all
768 quite a few other lists miss a way to search the archives. In those cases use a
870 problem: most of those shipped by distributors or add-on repositories are build
888 BUG occurs; if you plan to decode those, you might be better off compiling a
896 Those are likely a bit ahead of the latest mainline pre-release. Don't worry
906 those how-to's that suggest to use ``make localmodconfig``, as that tries to
914 latter is the relevant one of those two, but can only be reached if you enable
951 those). If you prefer to use one of those or just want to help their users,
1097 you are dealing with one of those 'issues of high priority': they need
1120 those rare cases where that's impossible try to describe what you did to
1138 In a lot of cases it's also wise to make two more things available to those
1208 Those examples should give your some ideas of what data might be wise to
1235 you, unless it's one of those 'issues of high priority' outlined earlier: in
1367 maintainers or all else fails, it might be one of those rare situations where
1373 mail you sent as reply to your report (make sure it has all those in the CC
1427 includes a full quote of the original report below: that's on of those few
1438 to move forward. That might mean: prepare a better report and make those people
1454 react somehow to every issue report, but they are only obliged to fix those
1602 fix you are hoping for might be one of those that won't be backported to the
1614 guide. Those steps will let you:
1725 work on the Linux kernel. Those contribute most changes these days. But their
1737 quite often are forced to set those, as time to work on Linux is limited.