| /OK3568_Linux_fs/kernel/drivers/pinctrl/intel/ |
| H A D | pinctrl-intel.c | 94 struct intel_community *community; in intel_get_community() local 98 community = &pctrl->communities[i]; in intel_get_community() 99 if (pin >= community->pin_base && in intel_get_community() 100 pin < community->pin_base + community->npins) in intel_get_community() 101 return community; in intel_get_community() 109 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument 114 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup() 115 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup() 127 const struct intel_community *community; in intel_get_padcfg() local 131 community = intel_get_community(pctrl, pin); in intel_get_padcfg() [all …]
|
| H A D | pinctrl-cherryview.c | 569 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_readl() local 571 return readl(community->regs + offset); in chv_pctrl_readl() 576 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_writel() local 577 void __iomem *reg = community->regs + offset; in chv_pctrl_writel() 587 const struct intel_community *community = &pctrl->communities[0]; in chv_padreg() local 593 return community->pad_regs + offset + reg; in chv_padreg() 1398 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_irq_handler() local 1411 for_each_set_bit(intr_line, &pending, community->nirqs) { in chv_gpio_irq_handler() 1468 const struct intel_community *community = &pctrl->communities[0]; in chv_init_irq_valid_mask() local 1482 if (intsel >= community->nirqs) in chv_init_irq_valid_mask() [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| 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 | 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 …]
|
| 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 | 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:
|
| H A 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 …]
|
| H A 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
|
| 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: 172 provide can help the development community provide useful input on the 188 community informed as you go.
|
| 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 207 some task to start doing to join into the kernel development community, 430 Working with the community 433 The goal of the kernel community is to provide the best possible kernel 458 In a community that is looking for the best technical solution possible, 472 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 194 kernel developer community as needed. Bringing in experts can happen at any 271 the Linux kernel community.
|
| /OK3568_Linux_fs/yocto/meta-clang/ |
| H A D | CODE_OF_CONDUCT.md | 7 our community a harassment-free experience for everyone, regardless of age, body 20 * Focusing on what is best for the community 21 * Showing empathy towards other community members 49 when an individual is representing the project or its community. Examples of 50 representing a project or community include using an official project e-mail
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ |
| H A D | ttf-takao_003.03.01.bb | 3 SUMMARY = "Takao Fonts are a community developed derivatives of IPA Fonts." 4 DESCRIPTION = "Takao Fonts are a community developed derivatives of IPA Fonts."
|
| H A D | ttf-lohit_2.92.1.bb | 5 to the community."
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/licenses/ |
| H A D | GPL-2.0-with-lmbench-restriction | 46 thing for the OS community and will stick to our guns on this one. 98 This helps protect the community from adopting flawed technologies 99 based on incomplete data. It also helps protect the community from 104 benchmark results have caused great harm to the community, and
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-support/openvpn/ |
| H A D | openvpn_2.5.6.bb | 10 SRC_URI = "http://swupdate.openvpn.org/community/releases/${BP}.tar.gz \ 15 UPSTREAM_CHECK_URI = "https://openvpn.net/community-downloads"
|
| /OK3568_Linux_fs/buildroot/board/freescale/imx6sabre/ |
| H A D | readme.txt | 169 https://community.freescale.com/docs/DOC-95015 170 https://community.freescale.com/docs/DOC-95017 171 https://community.freescale.com/docs/DOC-99218
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | resources.txt | 4 [[community-resources]] 8 information in its community and outside.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/ |
| H A D | SimPL-2.0 | 17 If you distribute the software or a Derived Work, you must give back to the community by: 32 - You do not abide by the "give back to the community" terms (your licensees get to keep their righ…
|
| H A D | Simple-2.0 | 13 If you distribute the software or a Derived Work, you must give back to the community by: 23 You do not abide by the "give back to the community" terms (your licensees get to keep their rights…
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/arch/arm64/boot/dts/marvell/ |
| H A D | armada-8040-mcbin-singleshot.dts | 5 * Device Tree file for MACCHIATOBin Armada 8040 community board platform
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| 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
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-support/db/db/ |
| H A D | fix-parallel-build.patch | 5 Upstream-Status: Inappropriate [as far as open source community is concerned, upstream is dead]
|