From 71df0cfa0fef8f94bd118ef9e950bc797d9c3893 Mon Sep 17 00:00:00 2001
From: Xi Ruoyao <xry111@xry111.site>
Date: Fri, 13 Dec 2024 12:47:17 +0800
Subject: [PATCH 1/2] kernel: Note that make mrproper shouldn't be run for
 rebuild

---
 chapter10/kernel.xml | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml
index 971703466..5aac36b8d 100644
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@ -466,6 +466,26 @@
       <command>chown -R 0:0</command> on the <filename
       class="directory">linux-&linux-version;</filename> directory to ensure
       all files are owned by user <emphasis>root</emphasis>.</para>
+
+      <para>If you are updating the configuration and rebuilding the kernel
+      from a retained kernel source tree, normally you should
+      <emphasis role='bold'>not</emphasis> run the
+      <command>make mrproper</command> command.  The command would purge
+      the <filename>.config</filename> file and all the
+      <filename class='extension'>.o</filename> files from the previous
+      build.  Despite it's easy to restore <filename>.config</filename> from
+      the copy in <filename class='directory'>/boot</filename>, purging all
+      the <filename class='extension'>.o</filename> files is still a waste:
+      for a simple configuration change, often only a few
+      <filename class='extension'>.o</filename> files need to be (re)built
+      and the kernel build system will correctly skip other
+      <filename class='extension'>.o</filename> files if they are not
+      purged.</para>
+
+      <para>On the other hand, if you've upgraded GCC, you should run
+      <command>make clean</command> to purge all the
+      <filename class='extension'>.o</filename> files from the previous
+      build, or the new build may fail.</para>
     </note>
 
     <warning>

From d095cba8b6bcf7dc12cd10991f72122dde8e8b1f Mon Sep 17 00:00:00 2001
From: Xi Ruoyao <xry111@xry111.site>
Date: Fri, 13 Dec 2024 12:48:23 +0800
Subject: [PATCH 2/2] kernel: Remove outdated note not to update kernel API
 headers

We now consider upgrading kernel API headers safe.
---
 chapter10/kernel.xml | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml
index 5aac36b8d..327e3de60 100644
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@ -497,17 +497,6 @@
       complete.</para>
     </warning>
 
-    <warning>
-      <para>The headers in the system's <filename
-      class="directory">include</filename> directory (<filename
-      class="directory">/usr/include</filename>) should
-      <emphasis>always</emphasis> be the ones against which Glibc was compiled,
-      that is, the sanitised headers installed in <xref
-      linkend="ch-tools-linux-headers"/>.  Therefore, they should
-      <emphasis>never</emphasis> be replaced by either the raw kernel headers
-      or any other kernel sanitized headers.</para>
-    </warning>
-
   </sect2>
 
   <sect2 id="conf-modprobe" role="configuration">