Home
last modified time | relevance | path

Searched refs:patch (Results 1 – 25 of 33) sorted by relevance

12

/qemu/docs/devel/
H A Dstable-process.rst28 If you think the patch would be important for users of the current release
33 How to get a patch into QEMU stable
36 There are various ways to get a patch into stable:
39 the patch by adding
45 to the patch description. By default, this will send a copy of the patch
49 * You can also reply to a patch and put ``qemu-stable@nongnu.org`` on copy
50 directly in your mail client if you think a previously submitted patch
53 * If a maintainer judges the patch appropriate for stable later on (or you
54 notify them), they will add the same line to the patch, meaning that
57 * If you judge an already merged patch suitable for stable, send a mail
[all …]
H A Dsubmitting-a-patch.rst1 .. _submitting-a-patch:
23 * - Sent as patch emails to ``qemu-devel@nongnu.org``
69 There's no point submitting a patch which is based on a released version
86 Split up longer patches into a patch series of logical code changes.
88 add a file to the makefile in patch one and then add the file itself in
89 patch two. (This rule is here so that people can later use tools like
108 semantic changes (or even function renames) are done in a separate patch
118 the patch, will reduce churn in trying to treat unrelated ``}`` lines in
121 Ideally, a code motion patch can be reviewed by doing::
123 git format-patch --stdout -1 > patch;
[all …]
H A Dsubmitting-a-pull-request.rst7 sent as simple patch emails to the mailing list (see our page on
8 :ref:`submitting-a-patch`
11 patch series we might ask a submitter to send a pull request. This page
19 do this is to use ``git format-patch --cover-letter`` to create the
24 retransmitted patch mails (for example, by using
25 ``--subject-prefix=PULL`` in your ``git format-patch`` command). This
29 **Each patch must have your own Signed-off-by: line** as well as that of
30 the original author if the patch was not written by you. This is because
31 with a pull request you're now indicating that the patch has passed via
46 fixed patch series as normal to the list; you can't put it in a pull
[all …]
H A Dcode-provenance.rst6 Certifying patch submissions
10 patch submissions they make to the project. To put it another way,
19 The addition of this line asserts that the author of the patch is contributing
62 If the person sending the mail is not one of the patch authors, they are
69 It is not uncommon for a patch to have contributions from multiple authors. In
71 line for each contributor involved in creation of the patch. Some edge cases:
78 of code as suggested fixes to a patch. The reviewers don't need to have
102 * **``Reviewed-by``**: when a QEMU community member reviews a patch on the
103 mailing list, if they consider the patch acceptable, they should send an
105 review a patch should add this even if they are also adding their
[all …]
H A Dtrivial-patches.rst21 **You should hint that your patch is a candidate by CCing
27 Since the trivial patch team rotates maintainership there is only one
40 that the patch is queued.
H A Dmaintainers.rst46 much other than throw the odd patch in.
82 The process is simple - simply send a patch to the list that updates
88 Once the patch is reviewed and merged the only other step is to make
H A Dindex-process.rst15 submitting-a-patch
H A Dindex.rst19 :ref:`submitting-a-patch` sections to avoid common pitfalls.
/qemu/tests/tcg/s390x/
H A Dprecise-smc-user.c12 extern __uint128_t __attribute__((__aligned__(1))) patch;
34 : [patch] "v" (patch) in main()
35 , [idx] "r" (sizeof(patch) - 1) in main()
/qemu/hw/i386/
H A Dvapic.c291 uint32_t pos, patch, offset; in update_rom_mapping() local
329 cpu_physical_memory_read(paddr + offset, &patch, sizeof(patch)); in update_rom_mapping()
330 patch = le32_to_cpu(patch); in update_rom_mapping()
331 patch += rom_state_vaddr - le32_to_cpu(s->rom_state.vaddr); in update_rom_mapping()
332 patch = cpu_to_le32(patch); in update_rom_mapping()
333 cpu_physical_memory_write(paddr + offset, &patch, sizeof(patch)); in update_rom_mapping()
543 const uint8_t *patch; in patch_hypercalls() local
555 patch = &vmcall_pattern[5]; in patch_hypercalls()
560 patch = &outl_pattern[5]; in patch_hypercalls()
564 cpu_physical_memory_write(rom_paddr + pos + 5, patch, 3); in patch_hypercalls()
/qemu/tests/docker/dockerfiles/debian-microblaze-cross.d/
H A Dbuild-toolchain.sh13 …-microblaze/recipes-devtools/gcc/gcc-12/0009-Patch-microblaze-Fix-atomic-boolean-return-value.patch
40 wget -O - ${GCC_PATCH0_URL} | patch -d src-gcc -p1
/qemu/docs/specs/
H A Dacpi_hest_ghes.rst80 (5) QEMU generates N ADD_POINTER commands, which patch addresses in the
84 (6) QEMU generates N ADD_POINTER commands, which patch addresses in the
88 (7) QEMU generates N ADD_POINTER commands for the firmware, which patch
H A Drapl-msr.rst17 .. _msr-filter-patch: https://patchwork.kernel.org/project/kvm/patch/20200916202951.23760-7-graf@am…
H A Dacpi_nvdimm.rst87 page and dynamically patch its address into an int32 object named "MEMA"
/qemu/
H A DREADME.rst77 format-patch' and/or 'git send-email' to format & send the mail to the
100 or even just for sending consecutive patch series revisions. It also
117 Your patch series will be sent and tagged as my-feature-v1 if you need to refer
128 Your patch series will be sent with 'v2' tag in the subject and the git tip
H A D.gitignore21 *.patch
H A D.gitattributes9 *.patch -text -whitespace
/qemu/tests/qtest/migration/
H A DMakefile29 * the header and the assembler differences in your patch submission.
/qemu/docs/system/riscv/
H A Dvirt.rst174 in 32-bit mode, use the rv32_defconfig configuration. A patch is required to
181 …//patchwork.kernel.org/project/linux-riscv/patch/20210627135117.28641-1-bmeng.cn@gmail.com/mbox/ >…
182 $ git am riscv.patch
H A Dsifive_u.rst162 in 32-bit mode, use the rv32_defconfig configuration. A patch is required to
169 …patchwork.kernel.org/project/linux-riscv/patch/20201219001356.2887782-1-atish.patra@wdc.com/mbox/ …
170 $ git am riscv.patch
/qemu/pc-bios/
H A Dedk2-licenses.txt189 === Start of sample patch email message ===
200 An extra message for the patch email which will not be considered part
205 === End of sample patch email message ===
207 === Notes for sample patch email ===
212 * git format-patch is one way to create this format
214 === Definitions for sample patch email ===
216 * "Repository" is the identifier of the repository the patch applies.
219 * "Branch" is the identifier of the branch the patch applies. This
424 === Start of sample patch email message ===
435 An extra message for the patch email which will not be considered part
[all …]
/qemu/docs/
H A Dpcie_pci_bridge.txt104 1) Build shpchp module with this patch http://www.spinics.net/lists/linux-pci/msg63052.html
105 2) Use kernel 4.14+ where the patch mentioned above is already merged.
/qemu/python/
H A DPACKAGE.rst23 patch submission process
/qemu/scripts/
H A Dget_maintainer.pl411 open(my $patch, "< $file")
421 while (<$patch>) {
442 close($patch);
/qemu/scripts/coccinelle/
H A Derrp-guard.cocci27 // which in turn produces extra patch hunks for no reason.

12