Lines Matching full:developers
22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers
55 developers. It might be all that's needed for people already familiar with
98 needs to get reported to the kernel developers separately, unless they are
106 Find out how and where its developers expect reports. Note: most of the
174 switch from 5.9.15 to 5.10.5 does not qualify). The developers want to fix such
178 * Check if the kernel developers still maintain the Linux kernel version
247 * The Linux kernel developers are well aware this process is complicated and
254 request fixes from developers in the upstream Linux kernel community: such
272 issues to the Linux kernel developers.
284 Like most programmers, Linux kernel developers don't like to spend time dealing
295 Linux kernel developers: an issue you face with one of them might have been
296 fixed by the Linux kernel developers months or years ago already; additionally,
299 issues with these kernels to the vendor. Its developers should look into the
308 developers in fact are willing to handle reports about issues occurring with
309 vendor kernels. If they do in the end highly depends on the developers and the
313 Sid or Fedora Rawhide. Some developers will also accept reports about issues
322 or heavily modified vendor kernel to the upstream Linux developers. But note,
363 developers might look for people that can provide additional information or
371 need to report your issue". The developers that should take care of the issue
384 Linus Torvalds and the leading Linux kernel developers want to see some issues
532 Linux kernel developers. Most of the time the easiest way to do that is:
553 needs to get reported to the kernel developers separately, unless they are
557 separately, as they might be handled by different developers. Describing
582 Linux developers want to fix badly, as such issues are even more unwanted than
584 people. The developers thus want to learn about such issues as quickly as
594 Find out how and where its developers expect reports. Note: most of the
599 big project and most of its developers are only familiar with a small subset of
606 file your issue and make it reach the developers that need to know about it.
609 kernel developers and experts. For everybody else the MAINTAINERS file is the
618 driver. If it's really something else, the driver's developers will get the
691 and might leave some work for other developers on the subsystem specific list;
729 modified during tree-wide cleanups by developers that do not care about the
783 programmers, Linux kernel developers don't like to spend time dealing with
821 more risky to use mainline during this period. Kernel developers are also often
877 **Using git**: Developers and experienced Linux users familiar with git are
1011 needed in your case, developers will tell you what to do.
1052 process. But keep in mind: it depends on the issue at hand if the developers
1094 Developers often get quite a lot of mail. They thus often just take a few
1192 subsystem developers provide <https://www.alsa-project.org/wiki/AlsaInfo>`_.
1196 Don't worry too much about forgetting something, as developers will ask for
1285 If your report was good and you are really lucky then one of the developers
1303 reply there and do not contact any of the developers privately about it. For
1337 In general, kernel developers will take one to five business days to respond to
1361 commitment and that you are willing to help. It also tells developers if the
1404 developers; or a discussion around the issue evolved, but faded out with
1473 *Check if the kernel developers still maintain the Linux kernel version
1481 need to check if the kernel developers still support the version line you care
1544 And note, it helps developers a great deal if you can specify the exact version
1602 * Check if the kernel developers still maintain the Linux kernel version line
1645 developers mailing list <https://lore.kernel.org/lkml/>`_. Also read the
1680 When reporting a problem to the Linux developers, be aware only 'issues of high
1683 will make sure of that. They and the other kernel developers will fix a lot of
1687 This is best explained with kernel developers that contribute to the Linux
1695 Then there are situations where such developers really want to fix an issue,
1700 Sooner or later spare time developers will also stop caring for the driver.
1710 The situation is not that different with developers that are paid for their
1724 That's true for spare time or the time employers grant their developers to
1738 issues to the Linux kernel developers: the length and complexity of this
1757 please use "The Linux kernel developers" for author attribution and link