From 472d58a06ec98f356ac18447e3f565b5cd1b5ca7 Mon Sep 17 00:00:00 2001 From: scott-lenovo Date: Tue, 8 Jan 2013 09:43:30 -0800 Subject: kernel-dev: First re-write of the "Patches" section. (From yocto-docs rev: 64e2b623e040efeefdef572024c867a57a883f24) Signed-off-by: scott-lenovo Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-advanced.xml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) (limited to 'documentation') diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index 7d82b54f65..12d3d7c8ec 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.xml +++ b/documentation/kernel-dev/kernel-dev-advanced.xml @@ -802,10 +802,13 @@ The description file can include multiple kconf statements, one per fragment. Patches - Patches are described in a very similar way to configuration - fragments, which are described in the previous section. - Instead of a .cfg file, they work with - source patches. + Patch descriptions are very similar to configuration fragment + descriptions, which are described in the previous section. + However, instead of a .cfg file, these + descriptions work with source patches. + + + A typical patch includes a description file and the patch itself: patches/mypatch.scc: @@ -814,8 +817,8 @@ The description file can include multiple kconf statements, one per fragment. patches/mypatch.patch: <typical-patch> - For .patch files, the typical patch - is created with diff -Nurp or + You can create the typical .patch + file using diff -Nurp or git format-patch. -- cgit v1.2.3-54-g00ecf