Lines Matching full:why

256    development community, and this document. That's why you can't demand
298 face, even if they look small or totally unrelated. That's why you should report
466 your kernel gets enhanced in any way. That's why you should remove or disable
475 module not part of the Linux kernel. That why your might need to uninstall the
487 be such an error if your kernel is tainted. That's why it's in your interest to
489 only reason why this step is here, as this process later will tell you to
497 why the kernel also mentions the taint status when it reports an internal
506 to find out why. Try to eliminate the reason. Often it's caused by one these
567 might be caused by a bit flip due to cosmic radiation. That's why you should
607 That's why you have to find the right place and way to report issues yourself.
742 as the reporter. That's why you should search for existing report again, now
785 waste everybody's time, especially yours. That's why it's in everybody's
824 window fixes the issue you face; that's why you soon would have to retest with
828 That's why it might make sense to wait till the merge window is over. But don't
837 must be applied to mainline first. That's why checking the latest mainline
844 These aspects are also why longterm kernels (sometimes called "LTS kernels")
918 unrelated. That's why you need to check if the kernel you just installed does
1021 worsens, that's why he deems regressions as unacceptable and wants to see them
1022 fixed quickly. That's why changes that introduced a regression are often
1089 That's why this text will only mention a few of the essentials as well as
1097 will look into it and help you. And that is why you should ignore them for now
1137 These two files are big, that's why it's a bad idea to put them directly into
1292 But this ideal scenario rarely happens. That's why the job is only starting
1343 here: maintainers should address them as soon as possible; that's why you
1380 many reasons why it's wise to quickly run an internet search to see who you're
1430 why the report did not get any replies. A good moment for this second reminder
1450 getting help are explained in 'Why some issues won't get any reaction or remain
1457 together that mentions how many you are and why this is something that in your
1480 chosen and gets supported for at least two years (often six). That's why you
1623 to get the issue solved. That's why you want to search for it or any
1677 Why some issues won't get any reaction or remain unfixed after being reported
1722 Priorities are another reason why some issues are not fixed, as maintainers