Lines Matching refs:code

139    decoding the kernel log to find the line of code that triggered the error.
285 with reports for issues that don't even happen with their current code. It's
357 the model line (Radeon 5700 or Radeon 5000) and the code name of the main chip
538     code (mostly drivers) that does not yet fulfill the normal Linux kernel
617 code it builds upon, but unless you suspect something like that stick to the
621 Sadly, there is no way to check which code is driving a particular hardware
671 that was replaced by a newer solution you need to switch to. Sometimes the code
673 'Orphan' you are totally out of luck, as nobody takes care of the code anymore.
685 maintainers of the particular code. Also look for a line starting with 'Mailing
686 list:', which tells you the public mailing list where the code is developed.
701 called with a path to the source code in question. For drivers compiled as
719 the code as well as the Linux Kernel Mailing List (LKML). In this case you thus
725 at the commit history to find which people recently worked on the code in
728 areas rarely changed (like old or unmaintained drivers): sometimes such code is
784 reports for issues that don't even happen with the current code. It's just a
786 interest that you confirm the issue still exists with the latest upstream code
846 the current code. Hence go and test mainline first and follow the process
902 you later to pinpoint the exact line of code that triggers your issue. The
964     decoding the kernel log to find the line of code that triggered the error.*
967 the executed code. This makes it possible to pinpoint the exact line in the
968 source code that triggered the issue and shows how it was called. But that only
989 the code the kernel was executing when the error occurred::
997 In this case the executed code was built from the file
1004 the code section the kernel was executing.
1036 code management system that's causing the regression. Once you find it, search
1147    happen if five or ten years from now a developer works on some code that was
1376 developer of the particular code area that will respond to your report. But as
1580 Even small and seemingly obvious code-changes sometimes introduce new and
1610 Check code history and search for existing discussions
1703 anymore. Sometimes developer stops caring for their code and Linux at all, as
1712 employers sooner or later also stop caring for their code or make its
1719 a company orphans some code, but as mentioned above: sooner or later they will
1720 leave the code behind, too.