Lines Matching full:but
38 The issue was fixed there, but you would like to see it resolved in a still
129 approach, but in that development phase it can be an even better idea to
216 above, but failed to reproduce your issue there; at the same time you want to
247 should be enough for most people. But sometimes there are situations where even
251 from top to bottom. But it's mainly meant to skim over and a place to look up
257 demands more than other FLOSS projects. We'd love to make it simpler. But
325 regular Fedora releases, and openSUSE Tumbleweed. But keep in mind, you better
331 or heavily modified vendor kernel to the upstream Linux developers. But note,
332 those often get rejected or ignored, so consider yourself warned. But it's still
364 But its exact brand name (say 'ASUS Red Devil Radeon RX 5700 XT Gaming OC')
405 increased power consumption also qualify as regression. But keep in mind: the
409 features; but to avoid regressions such features have to be enabled explicitly
432 runtime environment. It's hard to rule out that problem completely, but you
537 But don't invest too much time into this at this point of the process, as
623 You can do that with the help of a script (see below), but it mainly targets
632 code it builds upon, but unless you suspect something like that stick to the
651 But this approach won't work if your WiFi chip is connected over USB or some
668 but before doing so, try a somewhat shorted or modified name when searching the
741 question, as they might be able to help. But use these results with care, as it
761 But some list are hosted in different places. That for example is the case for
762 the ath10k WiFi driver used as example in the previous step. But you'll often
792 approach, but in that development phase it can be an even better idea to
802 before reporting it. You are free to ignore this advice, but as outlined
808 * Install a mainline kernel; the latest stable kernel can be an option, but
814 It also outlines that using a pre-compiled kernel are fine, but better are
843 That's why it might make sense to wait till the merge window is over. But don't
875 But you are in luck if you are using a popular Linux distribution: for quite a
898 development cycle is currently in the middle of a merge window. But even then
909 but quicker to compile.
914 latter is the relevant one of those two, but can only be reached if you enable
916 build a kernel by quite a bit. But that's worth it, as these options will allow
920 But keep in mind: Always keep a record of the issue encountered in case it is
948 line and abandoning your plan to report the issue. But keep in mind that other
967 thus easy to understand in written form. Include all important details, but at
983 source code that triggered the issue and shows how it was called. But that only
1040 get something quickly fixed. But for that to happen the change that's causing
1049 some time, but don't worry, it works a lot quicker than most people assume.
1067 process. But keep in mind: it depends on the issue at hand if the developers
1125 but there are some things you should include always:
1181 laptop mention its name, but try to make sure it's meaningful. 'Dell XPS 13'
1183 not that different from the one sold today, but apart from that the two have
1209 attach, but you have to think yourself what will be helpful for others to know.
1211 additional details they need. But making everything important available from
1283 the report's text to these addresses; but on top of it put a small note where
1306 But this ideal scenario rarely happens. That's why the job is only starting
1308 but often it will be the things listed below. But before digging into the
1331 * You were told to send something, but noticed it contains sensitive
1333 in private to the developer that asked for it. But note in the ticket or a
1341 a reply asking for instructions how to do that. But before going that route try
1347 within a few hours. But most of the time it will take longer, as maintainers
1378 idea, but only report your results if something relevant changed or if you are
1390 developer of the particular code area that will respond to your report. But as
1392 including people that want to help, but in the end might guide you totally off
1393 track with their questions or requests. That rarely happens, but it's one of
1407 possible fix, try to test it in timely manner, too. But do it properly and make
1410 proposed patch with a fix was applied, but in fact wasn't. Things like that
1411 happen even to experienced testers occasionally, but they most of the time will
1418 developers; or a discussion around the issue evolved, but faded out with
1454 react somehow to every issue report, but they are only obliged to fix those
1462 a fix. Such situations can be devastating, but is within the cards when it
1502 kernel.org front page for a week or two, but are unsuitable for testing and
1554 stable and regressions mailing list is all it takes; but in case you suspect
1584 reproduce your issue with a mainline kernel, but want to see it fixed in older
1601 longterm kernels, but too risky to integrate into older ones. So be aware the
1635 In a lot of cases the issue you deal with will have happened with mainline, but
1654 weeks, but sometimes it takes a bit longer.
1698 other issues as well. But be aware that sometimes they can't or won't help; and
1707 report. But nobody can force them to do, as they are contributing voluntarily.
1710 but can't: sometimes they lack hardware programming documentation to do so.
1725 work on the Linux kernel. Those contribute most changes these days. But their
1731 longer time period, but in new versions often leave support for old and rare
1733 a company orphans some code, but as mentioned above: sooner or later they will
1744 But don't worry too much about all of this, a lot of drivers have active
1753 document and the implications between the lines illustrate that. But that's how
1762 to contribute changes to the text, but for copyright reasons please CC