summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/kernel-dev')
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml20
1 files changed, 0 insertions, 20 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 4cceb932b6..688e12ac9a 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -130,26 +130,6 @@
130 detects the change in the recipe and fetches and applies the patches 130 detects the change in the recipe and fetches and applies the patches
131 before building the kernel. 131 before building the kernel.
132 </para> 132 </para>
133
134 <para>
135 Original Text:
136 <literallayout class='monospaced'>
137If you have a patch, or a small series of patches, to apply to the Linux kernel
138source, you can do so just as you would with any other recipe. You first copy
139the patches to the path added to FILESEXTRAPATHS in the bbappend file as
140described in 2.2 and then reference them in the SRC_URI.
141
142For example, you can apply a three patch series by adding the following lines to
143your linux-yocto bbappend file in your layer:
144
145 SRC_URI += "file://0001-first-change.patch"
146 SRC_URI += "file://0002-first-change.patch"
147 SRC_URI += "file://0003-first-change.patch"
148
149At the next build, bitbake will detect the change in the recipe and fetch and
150apply the patches before rebuilding the Linux kernel.
151 </literallayout>
152 </para>
153 </section> 133 </section>
154 134
155 <section id='changing-the-configuration'> 135 <section id='changing-the-configuration'>