| /openbmc/qemu/docs/devel/ |
| H A D | submitting-a-pull-request.rst | 1 .. _submitting-a-pull-request:
3 Submitting a Pull Request
8 :ref:`submitting-a-patch`
10 will need to submit pull requests, although occasionally for a large
11 patch series we might ask a submitter to send a pull request. This page
12 documents our recommendations on pull requests for those people.
14 A good rule of thumb is not to send a pull request unless somebody asks
17 **Resend the patches with the pull request** as emails which are
18 threaded as follow-ups to the pull request itself. The simplest way to
19 do this is to use ``git format-patch --cover-letter`` to create the
[all …]
|
| H A D | maintainers.rst | 11 - reviewing patches and suggesting changes
12 - collecting patches and preparing pull requests
13 - tending to the long term health of their area
14 - participating in other project activities
22 --------------------
25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__
34 .. list-table:: Meaning of support status in MAINTAINERS
36 :header-rows: 1
38 * - Status
39 - Meaning
[all …]
|
| H A D | trivial-patches.rst | 1 .. _trivial-patches:
7 --------
14 The trivial patches team take on the task of reviewing and building pull
15 requests for patches that:
17 - Do not fall under an actively maintained subsystem.
18 - Are single patches or short series (max 2-4 patches).
19 - Only touch a few lines of code.
22 qemu-trivial@nongnu.org.**
25 ------------
30 - git://github.com/vivier/qemu.git trivial-patches - `browse <https://github.com/vivier/qemu/tree/t…
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-soc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have
20 other top-level maintainers. The drivers/soc/ directory is generally meant
[all …]
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | pull-requests.rst | 1 Creating Pull Requests
4 This chapter describes how maintainers can create and submit pull requests
9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
23 the pull request on a separate branch. Typically you will base this branch
24 off of a branch in the developers tree whom you intend to send the pull
27 In order to create the pull request you must first tag the branch that you
33 Greg offers the following. A pull request with miscellaneous stuff for
34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
[all …]
|
| H A D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
76 the -rc releases) to move to.
[all …]
|
| H A D | configure-git.rst | 6 Tagged branches used in pull requests (see
7 Documentation/maintainer/pull-requests.rst) should be signed with the
9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same
10 key for the project, you can set it in the configuration and use the ``-s``
11 flag. To set the default ``key-id`` use::
34 ----------------------------------------
44 Link: https://lore.kernel.org/r/<message-id>
50 $ cat >.git/hooks/applypatch-msg <<'EOF'
52 . git-sh-setup
53 perl -pi -e 's|^Message-I[dD]:\s*<?([^>]+)>?$|Link: https://lore.kernel.org/r/$1|g;' "$1"
[all …]
|
| H A D | index.rst | 12 feature-and-driver-maintainers
13 configure-git
14 rebasing-and-merging
15 pull-requests
16 messy-diffstat
17 maintainer-entry-profile
18 modifying-patches
|
| /openbmc/openbmc/meta-security/ |
| H A D | README.md | 1 Master-next:
2 …//gitlab.com/akuster/meta-security/badges/master-next/pipeline.svg)](https://gitlab.com/akuster/me…
4 …tus](https://gitlab.com/akuster/meta-security/badges/master/pipeline.svg)](https://gitlab.com/akus…
6 Meta-security
9 The bbappend files for some recipes (e.g. linux-yocto) in this layer need
15 If meta-security is included, but security is not enabled as a
18 You have included the meta-security layer, but
35 URI: git://git.openembedded.org/openembedded-core
38 URI: git://git.openembedded.org/meta-openembedded/meta-oe
47 Assuming the security layer exists at the top-level of your
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/ |
| H A D | README.md | 1 meta-oe
6 URI: git://github.com/openembedded/openembedded-core.git
10 e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
14 pacman -S lib32-gcc-libs lib32-glibc
17 sudo apt-get install gcc-multilib linux-libc-dev:i386
19 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
22 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PAT…
24 You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
27 Note, it is discouraged to send patches via GitHub pull request system. Such
30 'git request-pull' to generate an email referencing your git repository.
[all …]
|
| /openbmc/qemu/.github/workflows/ |
| H A D | lockdown.yml | 1 # Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown
10 pull-requests: write
14 runs-on: ubuntu-latest
16 - uses: dessant/repo-lockdown@v2
18 pr-comment: |
21 This repository is a read-only mirror of the project's repostories hosted
22 on https://gitlab.com/qemu-project/qemu.git.
23 The project does not process merge requests filed on GitHub.
29 lock-pr: true
30 close-pr: true
|
| /openbmc/linux/Documentation/translations/zh_CN/maintainer/ |
| H A D | pull-requests.rst | 1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/maintainer/pull-requests.rst
28 --------
37 Greg提供了以下内容。对于一个含有drivers/char中混杂事项、将应用于4.15-rc1内核的
38 拉取请求，可以命名为 ``char-misc-4.15-rc1`` 。如果要在 ``char-misc-next`` 分支
41 git tag -s char-misc-4.15-rc1 char-misc-next
43 这将在 ``char-misc-next`` 分支的最后一个提交上创建一个名为 ``char-misc-4.15-rc1``
44 的标记，并用您的gpg密钥签名（参见 Documentation/maintainer/configure-git.rst ）。
79 Char/Misc patches for 4.15-rc1
81 Here is the big char/misc patch set for the 4.15-rc1 merge window.
[all …]
|
| H A D | index.rst | 1 .. include:: ../disclaimer-zh_CN.rst
16 configure-git
17 rebasing-and-merging
18 pull-requests
19 maintainer-entry-profile
20 modifying-patches
|
| H A D | configure-git.rst | 1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/maintainer/configure-git.rst
16 Documentation/maintainer/pull-requests.rst 中使用的标记分支应使用开发人员的
17 GPG公钥进行签名。可以通过将 ``-u`` 标志传递给 ``git tag`` 来创建签名标记。
40 -------------------------------
47 Link: https://lore.kernel.org/r/<message-id>
51 .. code-block:: none
54 $ cat >.git/hooks/applypatch-msg <<'EOF'
56 . git-sh-setup
57 perl -pi -e 's|^Message-Id:\s*<?([^>]+)>?$|Link: https://lore.kernel.org/r/$1|g;' "$1"
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | uncore-memory.json | 3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
7 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
13 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
17 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.…
54 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
59 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
63 …"PublicDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre : DRAM RD…
99 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.…
104 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre",
108 …"PublicDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre : DRAM …
[all …]
|
| /openbmc/linux/include/uapi/rdma/ |
| H A D | rvt-abi.h | 1 /* SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) */
41 * and stored in qp->r_rq.max_sge (or srq->rq.max_sge).
60 /* new work requests posted to the head */
62 /* receives pull requests from here. */
|
| /openbmc/docs/ |
| H A D | maintainer-workflow.md | 5 for sub-project maintainers to follow before approving patches.
7 - Manually verify the contributor has signed the ICLA (individual) or is listed
9 - Executed CLAs can be found [in the CLA repository][1].
10 - If you were not added to the appropriate CLA repository ACL send an email to
12 - If a CLA for the contributor is found, accept the patch(1).
13 - If a CLA is not found, request that the contributor execute one and send it to
15 - Do not accept the patch(1) until a signed CLA (individual _or_ corporate)
17 - The CCLA form can be found [here][2].
18 - The ICLA form can be found [here][3].
21 forks of upstream projects, like the Linux kernel or U-Boot.
[all …]
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
64 Shortly after the pull request has been created, the CI workflow will run. Note
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/ |
| H A D | README.md | 2 ------------
5 URI: git://git.openembedded.org/openembedded-core
8 URI: git://git.openembedded.org/meta-openembedded
11 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gnome]' in the subject'
14 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-gnome][P…
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/ |
| H A D | README.md | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
9 meta-xfce depends on meta-oe, meta-gnome and meta-multimedia in this repository.
11 To avoid dependencies on meta-multimedia you need to mask recipes by adding
14 BBMASK = "meta-xfce/recipes-multimedia"
16 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce]' in the subject'
19 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-xfce][PA…
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/ |
| H A D | README.md | 1 meta-initramfs
6 small-sized initramfs.
10 ------------
14 URI: git://git.openembedded.org/meta-openembedded
19 -----------
21 Send patches / pull requests to openembedded-devel@lists.openembedded.org
22 with '[meta-initramfs]' in the subject.
25 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-initramf…
31 -------
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/ |
| H A D | README.md | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
7 layers: meta-oe
10 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the sub…
13 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-multimed…
15 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded t…
|
| /openbmc/phosphor-misc/ |
| H A D | README.md | 1 # phosphor-misc
3 phosphor-misc is a collection of miscellaneous OpenBMC functions that doesn't
8 If you have a new function in mind to be hosted in phosphor-misc, it is usually
13 phosphor-misc patches are reviewed using the Gerrit instance at
14 <https://gerrit.openbmc-project.xyz>.
17 [here](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-se…
18 <https://github.com/openbmc/phosphor-misc> is a hosting mirror only and GitHub
19 pull requests are not monitored and will not be accepted.
23 - follow
24 …[the seven rules of a great git commit message](https://chris.beams.io/posts/git-commit/#seven-rul…
|
| /openbmc/openbmc/meta-openembedded/meta-python/ |
| H A D | README.md | 1 meta-python
5 -------------------------
10 -------------------------
12 The meta-python layer depends on:
14 URI: git://git.openembedded.org/openembedded-core
18 URI: git://git.openembedded.org/meta-openembedded
19 layers: meta-oe
23 -------------------------
25 The meta-openembedded mailinglist
26 (openembedded-devel@lists.openembedded.org) is used for questions,
[all …]
|
| /openbmc/linux/Documentation/accounting/ |
| H A D | cgroupstats.rst | 7 suggested by Andrew Morton in https://lore.kernel.org/r/20070411114927.1277d7c9.akpm@linux-foundati…
9 Per cgroup statistics infrastructure re-uses code from the taskstats
15 The current model for cgroupstats is a pull, a push model (to post
17 user space requests for statistics by passing the cgroup path.
28 ~/balbir/cgroupstats # ./getdelays -C "/sys/fs/cgroup/a"
30 ~/balbir/cgroupstats # ./getdelays -C "/sys/fs/cgroup"
|