| /linux/Documentation/process/ |
| H A D | researcher-guidelines.rst | 8 The Linux kernel community welcomes transparent research on the Linux
13 The community greatly appreciates if researchers can share preliminary
17 sharing open access copies of the published research with the community
20 This document seeks to clarify what the Linux kernel community considers
31 The Linux kernel community expects that everyone interacting with the
34 code) produced by the Linux kernel community is welcome, though research
51 contributors. As a general rule, though, the kernel community derives
56 themselves or to the kernel community as a whole. For this reason, this
59 Kernel community members already receive far too much email and are likely
61 such requests deprives the community of valuable contributor time and is
[all …]
|
| H A D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
25 * Focusing on what is best for the community
26 * Showing empathy towards other community members
58 when an individual is representing the project or its community. Examples of
59 representing a project or community include using an official project e-mail
86 kernel community will be interpreting this document.
|
| H A D | contribution-maturity-model.rst | 15 part of the Linux Kernel community need to allow engineers to be
24 expectations for upstream community engagement aim to increase the
35 upstream community.
70 * A Software Engineer’s community contributions will be considered in
98 * Organizations will consider community member feedback in official
106 * Organizations will actively seek out community member feedback as a
|
| H A D | kernel-enforcement-statement.rst | 9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
14 community and do not have an unintended negative impact on the health and
17 community to undertake the following commitment to users of the Linux kernel
21 it is in the best interests of our development community to adopt the
45 as a last resort, to be initiated only when other community efforts have
|
| H A D | 3.Early-stage.rst | 31 immediate problem. To the wider kernel community, though, it was seen as a
38 The audio community, however, could not see past the particular solution
55 - and to discuss it with the development community before investing in the
75 discussions with the community before launching into implementation. Early
95 Years of experience with the kernel development community have taught a
98 released into the community. Sometimes these problems are severe,
100 the kernel community's standards. Some examples include:
173 provide can help the development community provide useful input on the
189 community informed as you go.
|
| H A D | index.rst | 9 Working with the kernel development community
14 to learn about how our community works. Reading these documents will make
22 your entry into the kernel community.
55 These are the rules that we try to live by in the kernel community (and
106 Here are some other guides to the community that are of interest to most
|
| H A D | howto.rst | 8 to work with the Linux kernel development community. It tries to not
24 and hints on how to work with the community. It will also try to
25 explain some of the reasons why the community works like it does.
50 existing development community. It is a diverse group of people, with
79 invaluable for learning how to interact with the kernel community. When
206 some task to start doing to join into the kernel development community,
428 Working with the community
431 The goal of the kernel community is to provide the best possible kernel
456 In a community that is looking for the best technical solution possible,
470 Differences between the kernel community and corporate structures
[all …]
|
| H A D | embargoed-hardware-issues.rst | 78 unable to enter into any non-disclosure agreements. The kernel community
86 The Linux kernel community has a deep understanding of the requirement to
90 The Linux kernel community has successfully handled hardware security
92 community compliant development under embargo restrictions.
94 The Linux kernel community has a dedicated hardware security team for
108 effective deterrent in our community. In case a violation happens the
196 kernel developer community as needed. Any involved party can suggest
317 the Linux kernel community.
|
| H A D | cve.rst | 10 the kernel development community has tended to avoid them. However, the
13 outside of the kernel community has made it clear that the kernel
14 community should have control over those assignments.
114 tested together in a unified whole by many community members, and not as
|
| H A D | development-process.rst | 7 work with the development community with a minimum of frustration. It is
8 an attempt to document how this community works in a way which is
|
| H A D | 6.Followthrough.rst | 17 kernel community to ensure that your code is up to the kernel's quality
105 kernel development community; he can often unjam a situation which seems to
130 contents visible to the development community as a whole. At this point,
186 development community remembers developers who lose interest in their code
218 be hurtful and discouraging, but the community will remember your reaction
|
| H A D | conclave.rst | 34 and its community.
37 broader community, using the ksummit@lists.linux.dev mailing list, what
|
| H A D | maintainer-soc.rst | 77 community review. After positive community review, work should be sent to
86 the community.
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-maintainer-entry-profile.rst | 34 The Linux NFS community does not have any chat room.
44 community's bugzilla at:
68 The NFSD community strives to provide an NFS server implementation
163 contains several NFS-specific workflows, as well as the community
345 test environments, including community zero-day bots, static
376 CVEs are generated by specific members of the Linux kernel community
377 and several external entities. The Linux NFS community does not emit
400 The Linux kernel community as a whole is still exploring the new
457 the community.
485 Community roles and their authority
[all …]
|
| /linux/sound/soc/sof/ |
| H A D | sof-pci-dev.c | 115 /* all Up boards use the community key */
124 * All newer platforms use the community key
253 path_override->fw_path_postfix = "community"; in sof_pci_probe()
254 path_override->fw_lib_path_postfix = "community"; in sof_pci_probe()
|
| /linux/Documentation/scsi/ |
| H A D | FlashPoint.rst | 24 "Mylex is committed to supporting the Linux community," says Peter Shambora,
86 been problematic for members of the Linux community, in that no Linux
112 publicly about BusLogic's attitude toward the Linux community, and I felt
132 SCSI solution for the Linux community, and does not want to see anyone left
|
| H A D | lpfc.rst | 43 The community supporting kernel.org has driven an effort to remove
52 community in modifying the behavior of the SCSI midlayer so that SCSI
|
| /linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 93 by community members must not be redirected from public to closed forums
123 the community etc. etc. Even when there is clearly one perfect candidate,
146 - unknown to the community, never sent an email to the list before
|
| /linux/tools/testing/selftests/rcutorture/doc/ |
| H A D | rcu-test-image.txt | 60 https://help.ubuntu.com/community/KVM/CreateGuests
61 https://help.ubuntu.com/community/JeOSVMBuilder
|
| /linux/Documentation/arch/arc/ |
| H A D | arc.rst | 12 - `<https://embarc.org>`_ - Community portal for open source on ARC.
20 Other projects are developed by Synopsys and made available to community
|
| /linux/Documentation/ |
| H A D | index.rst | 16 Working with the development community
20 community and getting your work upstream.
|
| /linux/Documentation/gpu/ |
| H A D | introduction.rst | 108 As a freedesktop.org project, dri-devel, and the DRM community, follows the
112 interacting with community members on mailing lists, IRC, or bug
113 trackers. The community represents the project as a whole, and abusive
|
| /linux/drivers/net/ |
| H A D | LICENSE.SRC | 13 of ideas throughout the research community. All software is furnished
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | armada-8040-mcbin.dts | 5 * Device Tree file for MACCHIATOBin Armada 8040 community board platform
|
| H A D | armada-8040-mcbin-singleshot.dts | 5 * Device Tree file for MACCHIATOBin Armada 8040 community board platform
|