From 1fa2beffa185438ed0f3c1133bf1304b914c6ca0 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Thu, 27 Dec 2012 12:28:58 -0600
Subject: kernel-dev: Formatted the "Patches" section.

(From yocto-docs rev: e7de7e806d4cd02e4b5c8cb1ac237809bef5144e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/kernel-dev/kernel-dev-advanced.xml | 44 ++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

(limited to 'documentation')

diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 8a036a7d2d..c669357477 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -762,6 +762,50 @@ The description file can include multiple kconf statements, one per fragment.
         </para>
     </section>
 
+    <section id='patches'>
+        <title>Patches</title>
+
+        <para>
+            Patches are described in a very similar way to configuration
+            fragments, which are described in the previous section.
+            Instead of a <filename>.cfg</filename> file, they work with
+            source patches.
+            A typical patch includes a description file and the patch itself:
+            <literallayout class='monospaced'>
+     patches/mypatch.scc:
+        patch mypatch.patch
+
+     patches/mypatch.patch:
+        &lt;typical-patch&gt;
+            </literallayout>
+            For <filename>.patch</filename> files, the typical patch
+            is created with <filename>diff -Nurp</filename> or
+            <filename>git format-patch</filename>.
+        </para>
+
+        <para>
+            The description file can include multiple patch statements,
+            one per patch.
+        </para>
+
+        <para>
+            Original text:
+            <literallayout class='monospaced'>
+Patches are described in a very similar way to configuration fragments (see
+3.3.1). Instead of a .cfg file, they work with source patches. A typical patch
+includes a description file and the patch itself:
+
+patches/mypatch.scc:
+	patch mypatch.patch
+
+patches/mypatch.patch:
+	&lt;typical patch created with 'diff -Nurp' or 'git format-patch'&gt;
+
+The description file can include multiple patch statements, one per patch.
+            </literallayout>
+        </para>
+    </section>
+
 
 
 
-- 
cgit v1.2.3-54-g00ecf