From 6852a953fd18f3201675779bc4aacfe8bd713205 Mon Sep 17 00:00:00 2001 From: Paul Philippov Date: Mon, 28 Feb 2022 02:06:39 -0500 Subject: [PATCH] Update integration-kernel.md --- en/integration-kernel.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/en/integration-kernel.md b/en/integration-kernel.md index 573ed38..4f9338a 100644 --- a/en/integration-kernel.md +++ b/en/integration-kernel.md @@ -20,11 +20,11 @@ CONFIG_IP_PNP_DHCP=y CONFIG_ROOT_NFS=y ``` -## The patch names +## Patch files -``` -These patch files should be named -.patch. -The patch files coming with Buildroot should not contain any package version reference in their filename. -The field in the patch file name refers to the apply order, and shall start at 1 -It is preferred to pad the number with zeros up to 4 digits, like git-format-patch does. E.g.: 0001-foobar-the-buz.patch -``` \ No newline at end of file +Patch files should be named `-.patch`. +- The patch files should not contain any package version reference in their filename. +- The field `` in the patch file name refers to the apply order, and shall start at 1. +It is preferred to pad the number with zeros up to 4 digits, like git-format-patch does. E.g.: _0001-foobar-the-buz.patch_ +- A message explaining what the patch does, and why it is needed, should be added in the header commentary of the patch. +- You should add a Signed-off-by statement in the header of the each patch to help with keeping track of the changes and to certify that the patch is released under the same license as the software that is modified.