Home
last modified time | relevance | path

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

12345678910>>...24

/third_party/mindspore/tests/ut/python/dataset/
Dtest_slice_patches.py146 patches = slice_patches_op(image)
147 assert len(patches) == 16
148 assert patches[0].shape == (79, 16, 1)
153 patches = slice_patches_op(image)
154 assert len(patches) == 16
155 assert patches[0].shape == (79, 16)
171 patches = slice_patches_op(image)
172 assert len(patches) == 12
173 assert patches[0].shape == (14, 28, 256)
178 patches = slice_patches_op(image)
[all …]
/third_party/vk-gl-cts/scripts/verify/
Dpackage.py34 …def __init__ (self, basePath, statement, testLogs, gitStatus, gitLog, patches, summary, conformVer… argument
40 self.patches = patches
52 patches = []
69 patches.append(item)
76 …return PackageDescription(packagePath, statement, testLogs, gitStatus, gitLog, patches, summary, c…
/third_party/cJSON/
DcJSON_Utils.c1038 CJSON_PUBLIC(int) cJSONUtils_ApplyPatches(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatches() argument
1043 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatches()
1049 if (patches != NULL) in cJSONUtils_ApplyPatches()
1051 current_patch = patches->child; in cJSONUtils_ApplyPatches()
1067 …PUBLIC(int) cJSONUtils_ApplyPatchesCaseSensitive(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatchesCaseSensitive() argument
1072 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatchesCaseSensitive()
1078 if (patches != NULL) in cJSONUtils_ApplyPatchesCaseSensitive()
1080 current_patch = patches->child; in cJSONUtils_ApplyPatchesCaseSensitive()
1096 static void compose_patch(cJSON * const patches, const unsigned char * const operation, const unsig… in compose_patch() argument
1100 if ((patches == NULL) || (operation == NULL) || (path == NULL)) in compose_patch()
[all …]
/third_party/flutter/skia/third_party/externals/icu/
DREADME.chromium19 2. Review and apply patches/changes in "D. Local Modifications" if
20 necessary/applicable. Update patch files in patches/.
156 b. Drop local patches we used to have for the following issues. They'll
170 1. Applied locale data patches from Google obtained by diff'ing
173 - patches/locale_google.patch:
181 - patches/locale1.patch: Minor fixes for Korean
184 2. Breakiterator patches
185 - patches/wordbrk.patch for word.txt
191 - patches/khmer-dictbe.patch
197 patch: patches/cjdict.patch
[all …]
/third_party/skia/third_party/externals/icu/
DREADME.chromium20 2. Review and apply patches/changes in "D. Local Modifications" if
21 necessary/applicable. Update patch files in patches/.
146 b. Drop local patches we used to have for the following issues. They'll
157 1. Applied locale data patches from Google obtained by diff'ing
160 - patches/locale_google.patch:
168 - patches/locale1.patch: Minor fixes for Korean
171 2. Breakiterator patches
172 - patches/wordbrk.patch for word.txt
178 - patches/khmer-dictbe.patch
184 patch: patches/cjdict.patch
[all …]
/third_party/skia/third_party/externals/spirv-cross/reference/shaders-no-opt/asm/tesc/
Darray-of-block-output-initializer.asm.tesc22 } patches[2];
59 patches[0].v2 = _6_0_init[0];
63 patches[1].v2 = _6_0_init[1];
67 patches[0].v3 = _6_1_init[0];
71 patches[1].v3 = _6_1_init[1];
/third_party/libdrm/
DCONTRIBUTING.rst8 send-email. For patches only touching driver specific code one of the driver
15 libdrm" to make it easier to find libdrm patches. This is best done by running
31 Your patches should also include a Signed-off-by line with your name and email
41 We won't reject patches that lack S-o-b, but it is strongly recommended.
64 spelling fixes and whitespace adjustment) patches that have been merged
66 drivers, merged patches to those components also count towards the commit
71 peoples patches but just make sure that patch submission isn't one-way
74 - Will be regularly contributing further patches. This includes regular
102 patches that violate the documented merge criteria, will also be handled through
/third_party/mesa3d/docs/relnotes/
D18.1.7.rst59 - cherry-ignore: Add additional 18.2 only patches
60 - cherry-ignore: Add more 18.2 patches
61 - cherry-ignore: Add more 18.2 patches
62 - cherry-ignore: Add a couple of patches with > 1 fixes tags
63 - cherry-ignore: more 18.2 patches
/third_party/skia/third_party/externals/spirv-cross/shaders-no-opt/asm/tesc/
Darray-of-block-output-initializer.asm.tesc9 … OpEntryPoint TessellationControl %main "main" %gl_out %gl_InvocationID %_ %patches %v2 %v3 %verts
27 OpName %patches "patches"
47 OpDecorate %patches Location 2
82 %patches = OpVariable %_ptr_Output__arr_vert_patch_uint_2 Output %patches_zero
/third_party/grpc/third_party/rake-compiler-dock/rake_x86-linux/
DDockerfile18 COPY build/patches /work/patches/
25 rvm install \$v --patch \$(echo /work/patches/ruby-\$v/* | tr ' ' ','); \
47 COPY build/patches2 /work/patches/
49 ( git apply /work/patches/rake-compiler-1.1.0/*.patch || true )
51 ( git apply /work/patches/hoe-3.20.0/*.patch || true )
56 git apply /work/patches/ruby-2.7.0/*.patch && \
/third_party/grpc/third_party/rake-compiler-dock/rake_x86_64-linux/
DDockerfile18 COPY build/patches /work/patches/
25 rvm install \$v --patch \$(echo /work/patches/ruby-\$v/* | tr ' ' ','); \
47 COPY build/patches2 /work/patches/
49 ( git apply /work/patches/rake-compiler-1.1.0/*.patch || true )
51 ( git apply /work/patches/hoe-3.20.0/*.patch || true )
56 git apply /work/patches/ruby-2.7.0/*.patch && \
/third_party/wayland_standard/
DCONTRIBUTING.md4 Sending patches
13 repository, and then submit these patches for review through a merge request.
15 Wayland formerly accepted patches via `git-send-email`, sent to
18 Some old patches continue to be sent this way, and we may accept small new
19 patches sent to the list, but please send all new patches through GitLab merge
74 Your patches should also include a Signed-off-by line with your name and
82 We won't reject patches that lack S-o-b, but it is strongly recommended.
84 When you re-send patches, revised or not, it would be very good to document the
89 deserve, and the patches may cause redundant review effort.
92 Tracking patches and following up
[all …]
/third_party/mesa3d/docs/
Dsubmittingpatches.rst11 - Code patches should follow Mesa :doc:`coding
13 - Whenever possible, patches should only affect individual Mesa/Gallium
150 It should go without saying that patches must be tested. In general, do
153 You should always run the Mesa test suite before submitting patches. The
155 pass before patches will be accepted, this may mean you have to update
163 As mentioned at the beginning, patches should be bisectable. A good way
197 If you revise your patches based on code review and push an update to
198 your branch, you should maintain a **clean** history in your patches.
199 There should not be "fixup" patches in the history. The series should be
216 - Make sure your MR is closed if your patches get pushed outside of
[all …]
/third_party/skia/third_party/externals/angle2/third_party/r8/
DREADME.chromium23 * Refer to commit descriptions within "3pp/patches" directory.
54 * Apply patches:
56 git am $CHROMIUM_SRC/third_party/r8/patches/*.patch
58 * Save new patches. Change number if expecting more or fewer patches:
59 git format-patch -3 -o $CHROMIUM_SRC/third_party/r8/3pp/patches
60 * Submit these fixed patches and the bot will automatically retry.
/third_party/ltp/tools/sparse/sparse-src/Documentation/
Dsubmitting-patches.md1 Submitting patches
5 [Submitting Patches](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html)
18 …Sign your work](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#sign-your-wo…
/third_party/weston/
DCONTRIBUTING.md28 Sending patches
37 repository, and then submit these patches for review through a merge request.
39 Weston formerly accepted patches via `git-send-email`, sent to
42 Some old patches continue to be sent this way, and we may accept small new
43 patches sent to the list, but please send all new patches through GitLab merge
100 Your patches should also include a Signed-off-by line with your name and
110 We won't reject patches that lack S-o-b, but it is strongly recommended.
112 When you re-send patches, revised or not, it would be very good to document the
117 deserve, and the patches may cause redundant review effort.
120 Tracking patches and following up
[all …]
/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/X86/
DREADME-FPStack.txt8 http://gcc.gnu.org/ml/gcc-patches/2004-04/msg00659.html
44 http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02410.html
55 http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02006.html
56 http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02011.html
/third_party/node/doc/guides/
Dmaintaining-icu.md114 in `tools/icu/icu-generic.gyp` or add patch files to `tools/icu/patches`.
137 > See section below about floating patches to ICU.
166 > See section below about floating patches to ICU.
196 ## Floating patches to ICU
198 Floating patches are applied at `configure` time. The "patch" files
217 mkdir -p tools/icu/patches/63
220 mkdir -p tools/icu/patches/63/source/tools/toolutil/
224 tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp
227 (edit tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp )
236 INFO: Using floating patch "tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp" from "tools/ic…
[all …]
/third_party/cef/tools/
Dpatcher.py59 patches = scope["patches"]
63 for patch in patches:
84 (len(patches), results['apply'], results['skip'], results['fail']))
/third_party/mindspore/mindspore/explainer/explanation/_attribution/_perturbation/
Docclusion.py38patches = np.lib.stride_tricks.as_strided(array, shape=patches_shape, strides=strides_in_memory, w…
39 patches = patches.reshape((-1,) + window_size)
40 return patches
/third_party/ltp/tools/sparse/sparse-src/
D.gitignore37 patches-*
40 patches
/third_party/boost/libs/type_index/patched/
DREADME.md1 patches for Boost libraries to work without RTTI
4 Here are the patches that are TESTED and work well with RTTI disabled and enabled.
/third_party/pixman/
DREADME4 Questions, bug reports and patches should be directed to the pixman
46 Sending patches
49 The general workflow for sending patches is to first make sure that
62 In order for your patches to be accepted, please consider the
111 should expect to have the first versions of their patches rejected.
/third_party/gstreamer/gstplugins_good/
DREADME.static-linking75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch
/third_party/gstreamer/gstreamer/
DREADME.static-linking75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch

12345678910>>...24