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>
This commit is contained in:
Scott Rifenbark
2012-12-27 12:28:58 -06:00
committed by Richard Purdie
parent cc07a5e350
commit 1fa2beffa1

View File

@@ -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>