diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-27 12:28:58 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-01-16 15:59:11 +0000 |
| commit | 1fa2beffa185438ed0f3c1133bf1304b914c6ca0 (patch) | |
| tree | fc7891e475b1d64702b25e12c69a499f81925649 /documentation | |
| parent | cc07a5e350aaf622d8f1ea87fa29c32d03288112 (diff) | |
| download | ast2050-yocto-poky-1fa2beffa185438ed0f3c1133bf1304b914c6ca0.zip ast2050-yocto-poky-1fa2beffa185438ed0f3c1133bf1304b914c6ca0.tar.gz | |
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>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-advanced.xml | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index 8a036a7..c669357 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: + <typical-patch> + </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: + <typical patch created with 'diff -Nurp' or 'git format-patch'> + +The description file can include multiple patch statements, one per patch. + </literallayout> + </para> + </section> + |
