Lines Matching full:patch

17    You should test your patch in OpenHamrony supported boards, hi3516dv300,
22    should use git-format-patch to generate patches, and if it's a patchset,
28    And make sure your patch follow unified OpenHarmony patch format describe
37 3. Send patch to OpenHarmony mailing list
40      git send-email *.patch -to="kernel@openharmony.io" --suppress-cc=all
52 4. Mark "v1, v2, v3 ..." in your patch subject if you have multiple versions
55    Use --subject-prefix="PATCH v2" option to add v2 tag for patchset.
56      git format-patch --subject-prefix="PATCH v2" -1
59      Subject: [PATCH v2 01/27] fork: fix some -Wmissing-prototypes warnings
60      Subject: [PATCH v3] ext2: improve scalability of bitmap searching
62 5. Upstream your kernel patch to kernel community is strongly recommended.
67    patch.
73    patch, which certifies that you wrote it or otherwise have the right to
74    pass it on as an open-source patch. The rules are pretty simple: if you
108 Use unified patch format
116    messy, and then it's hard to figure out the original patch.
120    strict patch management will alleviate the pain to migrate patches
126 Patch format definition
137 If the patch is related to CVE or issue/bugzilla, then we need add the
147 	1) Why we should apply this patch
148 	2) What real problem in product does this patch resolved
150 	4) Other useful information for help to understand this patch or problem
152 The detail information is very useful for porting patch to another kenrel
155 1. stable patch
174 2. mainline patch:
195 3. ohos patch
218 The patch fixes a BUG_ON in the product: injecting single bit ECC error