Lines Matching full:often

72    will often be needed anyway to hunt down and fix issues.
282    will often be needed anyway to hunt down and fix issues.*
287 easily happen when it comes to the kernel and often leads to frustration on both
291 kernel.org: these kernels from these vendors are often ancient from the point of
292 Linux development or heavily modified, often both.
301 upstream or forward the report there. In practice that often does not work out
312 example often holds true for the mainline kernels shipped by Debian GNU/Linux
315 its only slightly modified; that for example is often the case for Arch Linux,
323 those often get rejected or ignored, so consider yourself warned. But it's still
336 Reporting an issue that someone else already brought forward is often a waste of
356 often is not much helpful, as it is too specific. Instead try search terms like
473 they often get set up silently when you install Nvidia's proprietary graphics
506 to find out why. Try to eliminate the reason. Often it's caused by one these
566 Note: it's often fruitless to report issues that only happened once, as they
702 module if often can be found with a command like this::
741 brought forward is often a waste of time for everyone involved, especially you
744 often find its archives on `lore.kernel.org <https://lore.kernel.org/>`_.
747 the ath10k WiFi driver used as example in the previous step. But you'll often
821 more risky to use mainline during this period. Kernel developers are also often
853 **Using a pre-compiled kernel**: This is often the quickest, easiest, and safest
856 from modified Linux sources. They are thus not vanilla and therefore often
878 often best served by obtaining the latest Linux kernel sources straight from the
886 **Conventional**: People unfamiliar with git are often best served by
1022 fixed quickly. That's why changes that introduced a regression are often
1027 down the culprit, as maintainers often won't have the time or setup at hand to
1032 will often require you to build about ten to twenty kernel images, trying to
1094 Developers often get quite a lot of mail. They thus often just take a few
1158 few suggestions what often is good to provide:
1294 but often it will be the things listed below. But before digging into the
1386 **Inquiries for data**: Often you will be asked to test something or provide
1459 or the change that introduced a regression, which often makes developing a fix
1480 chosen and gets supported for at least two years (often six). That's why you
1689 written by such programmers, often because they simply wanted to make their
1697 This often happens when the publicly available docs are superficial or the
1716 stopped selling years ago. Enterprise Linux distributors often care for a
1717 longer time period, but in new versions often leave support for old and rare
1718 hardware aside to limit the scope. Often spare time contributors take over once
1723 quite often are forced to set those, as time to work on Linux is limited.