| /linux-6.15/drivers/pinctrl/intel/ |
| H A D | pinctrl-intel.c | 154 pin < community->pin_base + community->npins) in intel_get_community() 185 if (!community) in intel_get_padcfg() 1129 is = community->regs + community->is_offset + gpp * 4; in intel_gpio_irq_ack() 1153 reg = community->regs + community->ie_offset + gpp * 4; in intel_gpio_irq_mask_unmask() 1154 is = community->regs + community->is_offset + gpp * 4; in intel_gpio_irq_mask_unmask() 1288 reg = community->regs + community->ie_offset + gpp * 4; in intel_gpio_irq() 1289 is = community->regs + community->is_offset + gpp * 4; in intel_gpio_irq() 1811 base = community->regs + community->ie_offset; in intel_pinctrl_suspend_noirq() 1815 base = community->regs + community->hostown_offset; in intel_pinctrl_suspend_noirq() 1921 base = community->regs + community->ie_offset; in intel_pinctrl_resume_noirq() [all …]
|
| H A D | pinctrl-intel-platform.c | 90 struct intel_community *community, in intel_platform_pinctrl_prepare_community() argument 102 community->padown_offset = offset; in intel_platform_pinctrl_prepare_community() 107 community->padcfglock_offset = offset; in intel_platform_pinctrl_prepare_community() 112 community->hostown_offset = offset; in intel_platform_pinctrl_prepare_community() 117 community->is_offset = offset; in intel_platform_pinctrl_prepare_community() 122 community->ie_offset = offset; in intel_platform_pinctrl_prepare_community() 145 community->ngpps = ngpps; in intel_platform_pinctrl_prepare_community() 146 community->gpps = gpps; in intel_platform_pinctrl_prepare_community() 169 community->barno = i; in intel_platform_pinctrl_prepare_soc_data() 170 community->pin_base = pins.npins; in intel_platform_pinctrl_prepare_soc_data() [all …]
|
| H A D | pinctrl-cherryview.c | 576 return readl(community->regs + offset); in chv_pctrl_readl() 1487 if (intsel >= community->nirqs) in chv_init_irq_valid_mask() 1527 gpp = &community->gpps[i]; in chv_gpio_add_pin_ranges() 1582 gpp = &community->gpps[i]; in chv_gpio_probe() 1615 struct intel_community *community; in chv_pinctrl_probe() local 1639 community = &pctrl->communities[0]; in chv_pinctrl_probe() 1641 if (IS_ERR(community->regs)) in chv_pinctrl_probe() 1642 return PTR_ERR(community->regs); in chv_pinctrl_probe() 1644 community->pad_regs = community->regs + FAMILY_PAD_REGS_OFF; in chv_pinctrl_probe() 1684 community->acpi_space_id, in chv_pinctrl_probe() [all …]
|
| /linux-6.15/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 80 the entire developer community's trust in the contributor (and the 90 When engaging with the developer community, sending a patch has [all …]
|
| 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 144 kernel community. 194 on the community. 210 community which operates on trust and respect. [all …]
|
| 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 103 Here are some other guides to the community that are of interest to most
|
| 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 | 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 | 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 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 156 community and customers to improve your product. [all …]
|
| 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 | 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 470 Differences between the kernel community and corporate structures 473 The kernel community works differently than most traditional corporate 499 Another way the kernel community is different than most traditional [all …]
|
| 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 | 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 | 2.Process.rst | 39 community) is merged into the mainline kernel. The bulk of changes for a 161 done without involving the community, but it is better to do this work 198 leave a poor impression in the development community. Merging code 349 community is git. Git is one of a number of distributed version control 350 systems being developed in the free software community. It is well tuned 389 lists. It is hard to be a fully-functioning member of the community 408 development community comes together as a whole; developers who avoid this 476 noise which is distracting for the development community as a whole, so, 478 introduce themselves to the community will not get the sort of reception 497 building respect with the rest of the development community.
|
| /linux-6.15/Documentation/mm/damon/ |
| H A D | maintainer-profile.rst | 77 could be particularly helpful for DAMON community members since it is developed 82 tool for DAMON community, which DAMON maintainer is committed to support. 89 DAMON community is maintaining two bi-weekly meetup series for community 92 The first one is for any discussion between every community member. No
|
| /linux-6.15/Documentation/filesystems/xfs/ |
| H A D | xfs-maintainer-entry-profile.rst | 34 elsewhere in the kernel community. 45 and nudge the community in that direction. 155 community. 174 This gives the community time to review the changes, to suggest other changes, 179 This allows the broader kernel community adequate time to test the
|
| /linux-6.15/Documentation/ |
| H A D | index.rst | 16 Working with the development community 20 community and getting your work upstream.
|
| /linux-6.15/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
|
| /linux-6.15/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-6.15/drivers/net/ |
| H A D | LICENSE.SRC | 13 of ideas throughout the research community. All software is furnished
|
| /linux-6.15/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
|
| 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
|