summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-18 14:45:52 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-16 15:59:06 +0000
commit74d43d3a11113c8d8183d95e8b6215ee164784f6 (patch)
treea62539ba3d96a6cdc9029406277a8f49fe401146 /documentation
parent1306d5ca591882089e975cf83a191526723126ad (diff)
downloadpoky-74d43d3a11113c8d8183d95e8b6215ee164784f6.tar.gz
kernel-dev: Re-write of the "Applying Patches" section.
(From yocto-docs rev: 6f72b0ca3e883cb03618c9f37c69cb1ab774a9fe) 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-common.xml31
1 files changed, 30 insertions, 1 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 8e6db4c255..fe134cc916 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -123,7 +123,35 @@ Project Board Support Package Developer's Guide.
123 <title>Applying Patches</title> 123 <title>Applying Patches</title>
124 124
125 <para> 125 <para>
126 If you have a patch, or a small series of patches, to apply to the Linux kernel 126 If you have a single patch or a small series of patches
127 that you want to apply to the Linux kernel source, you
128 can do so just as you would with any other recipe.
129 You first copy the patches to the path added to
130 <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink>
131 in your <filename>.bbappend</filename> file as described in
132 the previous section, and then reference them in
133 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
134 statements.
135 </para>
136
137 <para>
138 For example, you can apply a three-patch series by adding the
139 following lines to your linux-yocto <filename>.bbappend</filename>
140 file in your layer:
141 <literallayout class='monospaced'>
142 SRC_URI += "file://0001-first-change.patch"
143 SRC_URI += "file://0002-first-change.patch"
144 SRC_URI += "file://0003-first-change.patch"
145 </literallayout>
146 Then next time you run BitBake to build the Linux kernel, BitBake
147 detects the change in the recipe and fetches and applies the patches
148 before building the kernel.
149 </para>
150
151 <para>
152 Original Text:
153 <literallayout class='monospaced'>
154If you have a patch, or a small series of patches, to apply to the Linux kernel
127source, you can do so just as you would with any other recipe. You first copy 155source, you can do so just as you would with any other recipe. You first copy
128the patches to the path added to FILESEXTRAPATHS in the bbappend file as 156the patches to the path added to FILESEXTRAPATHS in the bbappend file as
129described in 2.2 and then reference them in the SRC_URI. 157described in 2.2 and then reference them in the SRC_URI.
@@ -137,6 +165,7 @@ your linux-yocto bbappend file in your layer:
137 165
138At the next build, bitbake will detect the change in the recipe and fetch and 166At the next build, bitbake will detect the change in the recipe and fetch and
139apply the patches before rebuilding the Linux kernel. 167apply the patches before rebuilding the Linux kernel.
168 </literallayout>
140 </para> 169 </para>
141 </section> 170 </section>
142 171