| /Linux-v5.4/drivers/pinctrl/intel/ |
| D | pinctrl-intel.c | 127 struct intel_community *community; in intel_get_community() local
131 community = &pctrl->communities[i]; in intel_get_community()
132 if (pin >= community->pin_base && in intel_get_community()
133 pin < community->pin_base + community->npins) in intel_get_community()
134 return community; in intel_get_community()
142 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument
147 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup()
148 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup()
160 const struct intel_community *community; in intel_get_padcfg() local
164 community = intel_get_community(pctrl, pin); in intel_get_padcfg()
[all …]
|
| D | pinctrl-cherryview.c | 169 const struct chv_community *community; member
698 return pctrl->community->ngroups; in chv_get_groups_count()
706 return pctrl->community->groups[group].name; in chv_get_group_name()
714 *pins = pctrl->community->groups[group].pins; in chv_get_group_pins()
715 *npins = pctrl->community->groups[group].npins; in chv_get_group_pins()
763 return pctrl->community->nfunctions; in chv_get_functions_count()
771 return pctrl->community->functions[function].name; in chv_get_function_name()
781 *groups = pctrl->community->functions[function].groups; in chv_get_function_groups()
782 *ngroups = pctrl->community->functions[function].ngroups; in chv_get_function_groups()
794 grp = &pctrl->community->groups[group]; in chv_pinmux_set_mux()
[all …]
|
| /Linux-v5.4/Documentation/process/ |
| 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.
|
| D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
8 open-source community is unique and the Linux kernel is no exception.
10 community will interpret it. We also do not expect this interpretation
28 kernel community, a "maintainer" is anyone who is responsible for a
41 That being said, our community is vast and broad, and there is no new
43 behave in the parts of the community where they are active. That
49 others in the community when needed. Do not be afraid to reach out to
83 the Code of Conduct. The kernel community is aware of that and provides
89 The Linux kernel community primarily interacts on a set of public email
98 Conduct. The Linux kernel community does not have an "official" project
[all …]
|
| D | index.rst | 8 Working with the kernel development community
13 to learn about how our community works. Reading these documents will make
35 Other guides to the community that are of interest to most developers are:
|
| 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
|
| D | development-process.rst | 22 work with the development community with a minimum of frustration. It is
23 an attempt to document how this community works in a way which is
|
| D | 1.Intro.rst | 13 availability to users, community support in many forms, and the ability to
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
81 Working with the kernel development community is not especially hard. But,
83 difficulties when trying to do kernel work. The kernel community has
93 community's ways (or, worse, who tries to flout or circumvent them) will
94 have a frustrating experience in store. The development community, while
101 community is always in need of developers who will help to make the kernel
103 join our community.
121 learning how to work with the kernel community and get their code into the
[all …]
|
| 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:
172 provide can help the development community provide useful input on the
188 community informed as you go.
|
| D | embargoed-hardware-issues.rst | 73 unable to enter into any non-disclosure agreements. The kernel community
81 The Linux kernel community has a deep understanding of the requirement to
85 The Linux kernel community has successfully handled hardware security
87 community compliant development under embargo restrictions.
89 The Linux kernel community has a dedicated hardware security team for
103 effective deterrent in our community. In case a violation happens the
189 kernel developer community as needed. Bringing in experts can happen at any
265 the Linux kernel community.
|
| 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
207 some task to start doing to join into the kernel development community,
429 Working with the community
432 The goal of the kernel community is to provide the best possible kernel
457 In a community that is looking for the best technical solution possible,
471 Differences between the kernel community and corporate structures
[all …]
|
| D | 2.Process.rst | 39 community) is merged into the mainline kernel. The bulk of changes for a
166 done without involving the community, but it is better to do this work
203 leave a poor impression in the development community. Merging code
354 community is git. Git is one of a number of distributed version control
355 systems being developed in the free software community. It is well tuned
394 lists. It is hard to be a fully-functioning member of the community
413 development community comes together as a whole; developers who avoid this
480 noise which is distracting for the development community as a whole, so,
482 introduce themselves to the community will not get the sort of reception
501 building respect with the rest of the development community.
|
| D | 6.Followthrough.rst | 17 kernel community to ensure that your code is up to the kernel's quality
98 kernel development community; he can often unjam a situation which seems to
123 contents visible to the development community as a whole. At this point,
179 development community remembers developers who lose interest in their code
211 be hurtful and discouraging, but the community will remember your reaction
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 35 https://help.ubuntu.com/community/KVM/CreateGuests
36 https://help.ubuntu.com/community/JeOSVMBuilder
|
| /Linux-v5.4/arch/arm64/boot/dts/marvell/ |
| D | armada-8040-mcbin-singleshot.dts | 5 * Device Tree file for MACCHIATOBin Armada 8040 community board platform
|
| D | armada-8040-mcbin.dts | 5 * Device Tree file for MACCHIATOBin Armada 8040 community board platform
|
| /Linux-v5.4/drivers/net/ |
| D | LICENSE.SRC | 13 of ideas throughout the research community. All software is furnished
|
| /Linux-v5.4/Documentation/gpu/ |
| 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-v5.4/Documentation/scsi/ |
| D | lpfc.txt | 45 The community supporting kernel.org has driven an effort to remove
54 community in modifying the behavior of the SCSI midlayer so that SCSI
|
| D | FlashPoint.txt | 18 "Mylex is committed to supporting the Linux community," says Peter Shambora,
73 been problematic for members of the Linux community, in that no Linux
99 publicly about BusLogic's attitude toward the Linux community, and I felt
119 SCSI solution for the Linux community, and does not want to see anyone left
|
| /Linux-v5.4/Documentation/ |
| D | index.rst | 67 The kernel community is quite large, with thousands of developers
68 contributing over the course of a year. As with any large community,
|
| /Linux-v5.4/Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 43 | https://community.mellanox.com/s/article/howto-configure-arfs-on-connectx-4
54 | Enables `Data Center Bridging (DCB) Support <https://community.mellanox.com/s/article/howto-au…
68 | 1) `Legacy SRIOV mode (L2 mac vlan steering based) <https://community.mellanox.com/s/ar…
98 | Provides low-level InfiniBand/RDMA and `RoCE <https://community.mellanox.com/s/article/recommen…
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 115 - OMAP3 BeagleBoard : Low cost community board
124 - OMAP4 PandaBoard : Low cost community board
142 - AM335X Bone : Low cost community board
|
| /Linux-v5.4/net/ipv4/netfilter/ |
| D | nf_nat_snmp_basic.asn1 | 6 community
|
| /Linux-v5.4/Documentation/translations/ |
| D | index.rst | 51 If you need to communicate with the Linux community but you do not feel
|
