Home
last modified time | relevance | path

Searched refs:patches (Results 1 – 25 of 644) sorted by relevance

12345678910>>...26

/OK3568_Linux_fs/buildroot/boot/grub2/
H A D0058-gnulib-regexec-Fix-possible-null-dereference.patch20 grub-core/lib/gnulib-patches/fix-regexec-null-deref.patch | 12 ++++++++++++
23 create mode 100644 grub-core/lib/gnulib-patches/fix-regexec-null-deref.patch
31 grub-core/lib/gnulib-patches/fix-null-deref.patch \
32 grub-core/lib/gnulib-patches/fix-null-state-deref.patch \
33 + grub-core/lib/gnulib-patches/fix-regexec-null-deref.patch \
34 grub-core/lib/gnulib-patches/fix-uninit-structure.patch \
35 grub-core/lib/gnulib-patches/fix-unused-value.patch \
36 grub-core/lib/gnulib-patches/fix-width.patch \
43 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-deref.patch
44 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-state-deref.patch
[all …]
H A D0059-gnulib-regcomp-Fix-uninitialized-re_token.patch19 .../lib/gnulib-patches/fix-regcomp-uninit-token.patch | 15 +++++++++++++++
22 create mode 100644 grub-core/lib/gnulib-patches/fix-regcomp-uninit-token.patch
30 grub-core/lib/gnulib-patches/fix-null-deref.patch \
31 grub-core/lib/gnulib-patches/fix-null-state-deref.patch \
32 + grub-core/lib/gnulib-patches/fix-regcomp-uninit-token.patch \
33 grub-core/lib/gnulib-patches/fix-regexec-null-deref.patch \
34 grub-core/lib/gnulib-patches/fix-uninit-structure.patch \
35 grub-core/lib/gnulib-patches/fix-unused-value.patch \
42 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-deref.patch
43 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-state-deref.patch
[all …]
H A D0056-gnulib-regcomp-Fix-uninitialized-token-structure.patch21 grub-core/lib/gnulib-patches/fix-uninit-structure.patch | 11 +++++++++++
24 create mode 100644 grub-core/lib/gnulib-patches/fix-uninit-structure.patch
33 grub-core/lib/gnulib-patches/fix-null-deref.patch \
34 + grub-core/lib/gnulib-patches/fix-uninit-structure.patch \
35 grub-core/lib/gnulib-patches/fix-unused-value.patch \
36 grub-core/lib/gnulib-patches/fix-width.patch \
37 grub-core/lib/gnulib-patches/no-abort.patch \
45 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-deref.patch
46 +EXTRA_DIST += grub-core/lib/gnulib-patches/fix-uninit-structure.patch
47 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-unused-value.patch
[all …]
H A D0057-gnulib-argp-help-Fix-dereference-of-a-possibly-NULL-.patch19 grub-core/lib/gnulib-patches/fix-null-state-deref.patch | 12 ++++++++++++
22 create mode 100644 grub-core/lib/gnulib-patches/fix-null-state-deref.patch
31 grub-core/lib/gnulib-patches/fix-null-deref.patch \
32 + grub-core/lib/gnulib-patches/fix-null-state-deref.patch \
33 grub-core/lib/gnulib-patches/fix-uninit-structure.patch \
34 grub-core/lib/gnulib-patches/fix-unused-value.patch \
35 grub-core/lib/gnulib-patches/fix-width.patch \
43 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-deref.patch
44 +EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-state-deref.patch
45 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-uninit-structure.patch
[all …]
H A D0055-gnulib-regexec-Resolve-unused-variable.patch24 grub-core/lib/gnulib-patches/fix-unused-value.patch | 14 ++++++++++++++
27 create mode 100644 grub-core/lib/gnulib-patches/fix-unused-value.patch
36 grub-core/lib/gnulib-patches/fix-null-deref.patch \
37 + grub-core/lib/gnulib-patches/fix-unused-value.patch \
38 grub-core/lib/gnulib-patches/fix-width.patch \
39 grub-core/lib/gnulib-patches/no-abort.patch \
48 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-null-deref.patch
49 +EXTRA_DIST += grub-core/lib/gnulib-patches/fix-unused-value.patch
50 EXTRA_DIST += grub-core/lib/gnulib-patches/fix-width.patch
51 EXTRA_DIST += grub-core/lib/gnulib-patches/no-abort.patch
[all …]
/OK3568_Linux_fs/buildroot/docs/manual/
H A Dcustomize-patches.txt4 [[customize-patches]]
5 === Adding project-specific patches
7 It is sometimes useful to apply 'extra' patches to packages - on top of
14 patches.
17 +<packagename>+, patches are applied from +BR2_GLOBAL_PATCH_DIR+ as
33 * If a +series+ file exists in the package directory, then patches are
42 For information about how patches are applied for a package, see
50 will allow a user to manage their patches from one top-level
54 specifying custom patches is +BR2_LINUX_KERNEL_PATCH+.
55 +BR2_LINUX_KERNEL_PATCH+ should be used to specify kernel patches that
[all …]
H A Dpatch-policy.txt13 the builds. It supports three ways of applying patch sets: downloaded patches,
14 patches supplied within buildroot and patches located in a user-defined
17 === Providing patches
35 Most patches are provided within Buildroot, in the package
47 - Previously, it was mandatory for patches to be prefixed with the name of
50 not prefix patches with the package name.'
61 containing global package patches. See xref:customize-patches[] for
65 === How patches are applied
71 . If +<packagename>_PATCH+ is defined, then patches from these
78 * If a +series+ file exists in the package directory, then patches are
[all …]
H A Dcustomize-directory-structure.txt31 | +-- patches/
35 | +-- <some other patches>
89 | +-- patches/
99 +-- patches/
107 BR2_GLOBAL_PATCH_DIR="board/<company>/common/patches board/<company>/fooboard/patches"
110 then first the patches from the 'common' layer would be applied,
111 followed by the patches from the 'fooboard' layer.
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-multimedia/id3lib/
H A Did3lib_3.8.3.bb21 # patches maintained by quilt. So manually apply them before applying other local
22 # patches. Also remove all temp files before leaving, because do_patch() will pop
23 # up all previously applied patches in the start
27 # it's important that we only pop the existing patches when they've
29 # and reverse out some completely different set of patches
30 if [ -d ${S}/patches ]; then
35 QUILT_PATCHES=${S}/patches quilt pop -a
40 QUILT_PATCHES=${S}/debian/patches quilt pop -a
43 QUILT_PATCHES=${S}/debian/patches quilt push -a
/OK3568_Linux_fs/external/camera_engine_rkaiq/rkaiq/iq_parser_v2/j2s/
H A DcJSON_Utils.cpp1041 CJSON_PUBLIC(int) cJSONUtils_ApplyPatches(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatches() argument
1046 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatches()
1052 if (patches != NULL) in cJSONUtils_ApplyPatches()
1054 current_patch = patches->child; in cJSONUtils_ApplyPatches()
1070 …PUBLIC(int) cJSONUtils_ApplyPatchesCaseSensitive(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatchesCaseSensitive() argument
1075 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatchesCaseSensitive()
1081 if (patches != NULL) in cJSONUtils_ApplyPatchesCaseSensitive()
1083 current_patch = patches->child; in cJSONUtils_ApplyPatchesCaseSensitive()
1099 static void compose_patch(cJSON * const patches, const unsigned char * const operation, const unsig… in compose_patch() argument
1103 if ((patches == NULL) || (operation == NULL) || (path == NULL)) in compose_patch()
[all …]
/OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/selftest/cases/
H A Drecipeutils.py30 …patches = oe.recipeutils.patch_recipe(rd, rd.getVar('FILE'), vals, patch=True, relpath=metaselftes…
54 for f in patches:
68 …patches = oe.recipeutils.patch_recipe(rd, rd.getVar('FILE'), vals, patch=True, relpath=metaselftes…
82 for f in patches:
93 …patches = oe.recipeutils.patch_recipe(rd, rd.getVar('FILE'), vals, patch=True, relpath=metaselftes…
107 for f in patches:
/OK3568_Linux_fs/kernel/Documentation/process/
H A Dapplying-patches.rst19 In addition to explaining how to apply and revert patches, a brief
21 their specific patches) is also provided.
144 If you don't have any third-party patches applied to your kernel source, but
145 only patches from kernel.org and you apply the patches in the correct order,
157 in the wrong directory. Less often, you'll find patches that need to be
203 So if you get these errors with kernel.org patches then you should probably
216 generate a patch representing the differences between two patches and then
220 step. The -z flag to interdiff will even let you feed it patches in gzip or
232 downloading and applying of patches (https://www.selenic.com/ketchup/).
241 Where can I download the patches?
[all …]
H A Demail-clients.rst11 end, maintainers use ``git am`` to apply the patches.
29 for patches and other emails alike. https://useplaintext.email may be useful
33 Email clients that are used for Linux kernel patches should send the
37 Don't send patches with ``format=flowed``. This can cause unexpected
44 Emailed patches should be in ASCII or UTF-8 encoding only.
51 Copy-and-paste (or cut-and-paste) usually does not work for patches
56 Don't use PGP/GPG signatures in mail that contains patches.
57 This breaks many scripts that read and apply the patches.
61 and successfully apply it with 'patch' before sending patches to Linux
69 patches for the Linux kernel. These are not meant to be complete
[all …]
H A D5.Posting.rst3 Posting patches
9 of conventions and procedures which are used in the posting of patches;
13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`,
21 There is a constant temptation to avoid posting patches before they are
22 completely "ready." For simple patches, that is not a problem. If the
31 patches which are known to be half-baked, but those who do will come in
35 Before creating patches
39 sending patches to the development community. These include:
64 The preparation of patches for posting can be a surprising amount of work,
82 up patches is a bit of an art; some developers spend a long time figuring
[all …]
H A D2.Process.rst36 merging of patches for each release. At the beginning of each development
41 this time, at a rate approaching 1,000 changes ("patches," or "changesets")
57 Over the next six to ten weeks, only patches which fix problems should be
93 serious. For this reason, patches which cause regressions are looked upon
216 How patches get into the Kernel
219 There is exactly one person who can merge patches into the mainline kernel
220 repository: Linus Torvalds. But, for example, of the over 9,500 patches
238 maintainers to track a list of patches, including authorship information
240 patches in his or her repository are not found in the mainline.
243 the patches they have selected for merging from their repositories. If
[all …]
/OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-netkit/netkit-rwho/
H A Dnetkit-rwho_0.17.bb24 # patches maintained by quilt. So manually apply them before applying other local
25 # patches. Also remove all temp files before leaving, because do_patch() will pop
26 # up all previously applied patches in the start
30 # it's important that we only pop the existing patches when they've
32 # and reverse out some completely different set of patches
33 if [ -d ${S}/patches ]; then
38 QUILT_PATCHES=${S}/patches quilt pop -a
43 QUILT_PATCHES=${S}/debian/patches quilt pop -a
46 QUILT_PATCHES=${S}/debian/patches quilt push -a
/OK3568_Linux_fs/yocto/poky/meta/lib/oe/
H A Dpatch.py75 self.patches = []
207 patches = f.readlines()
209 for p in reversed(patches):
211 patches = []
213 self._removePatch(os.path.join(self.patchdir, patches[-1].strip()))
214 patches.pop()
216 for p in patches:
227 self.patches.insert(i, patch)
259 bb.note("patches is %s" % self.patches)
261 for i in self.patches:
[all …]
/OK3568_Linux_fs/kernel/Documentation/bpf/
H A Dbpf_devel_QA.rst6 workflows related to reporting bugs, submitting patches, and queueing
7 patches for stable kernels.
9 For general information about submitting patches, please refer to
44 Submitting patches
47 Q: To which mailing list do I need to submit my BPF patches?
49 A: Please submit your BPF patches to the bpf kernel mailing list:
56 the changes and provide their Acked-by's to the patches.
58 Q: Where can I find patches currently under discussion for BPF subsystem?
60 A: All patches that are Cc'ed to netdev are queued for review under netdev
65 Those patches which target BPF, are assigned to a 'bpf' delegate for
[all …]
/OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/process/
H A D5.Posting.rst15 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`,
148 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
159 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
166 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
174 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
/OK3568_Linux_fs/kernel/Documentation/livepatch/
H A Dcumulative-patches.rst5 There might be dependencies between livepatches. If multiple patches need
7 an order in which the patches will be installed. And function implementations
10 This might become a maintenance nightmare. Especially when more patches
30 Once the transition is finished, all older patches are automatically
65 to reverse it and restore the replaced patches atomically.
78 executed. Any callbacks from the replaced patches are ignored.
83 As a result, it might be dangerous to replace newer cumulative patches by
93 enabled patches were called.
/OK3568_Linux_fs/kernel/drivers/scsi/aic7xxx/aicasm/
H A Daicasm.c74 STAILQ_HEAD(patch_list, patch) patches;
126 STAILQ_INIT(&patches); in main()
425 for (cur_patch = STAILQ_FIRST(&patches); in output_code()
429 cur_patch == STAILQ_FIRST(&patches) ? "" : ",\n", in output_code()
493 pinfo = &scope->patches[patch]; in emit_patch()
515 STAILQ_INSERT_TAIL(&patches, new_patch, links); in emit_patch()
596 cur_patch = STAILQ_FIRST(&patches); in output_listing()
804 cur_scope->patches[1].skip_patch = in process_scope()
806 cur_scope->patches[1].skip_instr = in process_scope()
816 cur_scope->patches[0].skip_patch = patch0_patch_skip; in process_scope()
[all …]
/OK3568_Linux_fs/kernel/Documentation/maintainer/
H A Dmaintainer-entry-profile.rst7 (submitting-patches, submitting drivers...) with
18 tells the contributor where to send patches for which files, it does not
24 - Are there notifications when patches are applied to the local tree, or
47 require published specifications at a certain revision before patches
53 One of the common misunderstandings of submitters is that patches can be
55 considered for the next -rc1. The reality is that most patches need to
58 week) that patches might be considered for merging and when patches need to
/OK3568_Linux_fs/u-boot/tools/patman/
H A DREADME13 - Runs the patches through checkpatch.pl and its own checks
31 patches automatically (unless you use -m to disable this).
48 patches. Weeks later, change the patches and repeat, knowing that you
63 out where to send patches pretty well.
87 If you want to avoid sending patches to email addresses that are picked up
136 If it can't detect the upstream branch, try telling it how many patches
180 RFC patches, or RESEND if you are being ignored. The patch subject
222 A sign-off is added automatically to your patches (this is
223 probably a bug). If you put this tag in your patches, it will
274 patch series and see how the patches turn out.
[all …]
/OK3568_Linux_fs/kernel/
H A DREADME.md1 # How do I submit patches to Android Common Kernels
4 …These patches will be merged automatically in the corresponding common kernels. If the patch is al…
6 …- Do not send patches upstream that contain only symbol exports. To be considered for upstream Lin…
9 - When sending patches upstream, the commit message must contain a clear case for why the patch
13 2. LESS GOOD: Develop your patches out-of-tree (from an upstream Linux point-of-view). Unless these…
20 - All patches must conform to the Linux kernel coding standards and pass `script/checkpatch.pl`
25 - All patches must have a `Change-Id:` tag (see https://gerrit-review.googlesource.com/Documentatio…
27 - All patches must have a `Signed-off-by:` tag by the author and the submitter
114 - add a `Bug:` tag with the Android bug (required for patches not accepted into
131 ## Requirements for Android-specific patches: `ANDROID:`
/OK3568_Linux_fs/buildroot/package/setserial/
H A Dsetserial.mk18 if [ -d $(@D)/debian/patches ]; then \
20 rm $(@D)/debian/patches/01_makefile.dpatch; \
21 $(APPLY_PATCHES) $(@D) $(@D)/debian/patches *.dpatch; \

12345678910>>...26