From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: [PATCH] uapi: edd: update outdated file references in the header comments
Date: Tue, 14 Jul 2026 02:45:03 +0500 [thread overview]
Message-ID: <20260713214503.34685-1-kuleshovmail@gmail.com> (raw)
The header comment in <linux/edd.h> and <uapi/linux/edd.h> refers to
arch/{i386,x86_64}/boot/setup.S and arch/{i386,x86_64}/kernel/setup.c.
These paths have been stale since the i386 and x86_64 trees were unified
under arch/x86.
Update the outdated references to point at the current locations.
Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
---
include/linux/edd.h | 13 ++++++-------
include/uapi/linux/edd.h | 13 ++++++-------
2 files changed, 12 insertions(+), 14 deletions(-)
diff --git a/include/linux/edd.h b/include/linux/edd.h
index 1c16fbcb81c0..225719403e78 100644
--- a/include/linux/edd.h
+++ b/include/linux/edd.h
@@ -10,13 +10,12 @@
* available at http://www.t13.org/docs2002/d1572r0.pdf. It is
* very similar to D1484 Revision 3 http://www.t13.org/docs2002/d1484r3.pdf
*
- * In a nutshell, arch/{i386,x86_64}/boot/setup.S populates a scratch
- * table in the boot_params that contains a list of BIOS-enumerated
- * boot devices.
- * In arch/{i386,x86_64}/kernel/setup.c, this information is
- * transferred into the edd structure, and in drivers/firmware/edd.c, that
- * information is used to identify BIOS boot disk. The code in setup.S
- * is very sensitive to the size of these structures.
+ * In a nutshell, arch/x86/boot/edd.c populates a scratch table in the
+ * boot_params that contains a list of BIOS-enumerated boot devices.
+ * In arch/x86/kernel/setup.c, this information is transferred into
+ * the edd structure, and in drivers/firmware/edd.c, that information
+ * is used to identify BIOS boot disk. The boot code is very sensitive
+ * to the size of these structures.
*/
#ifndef _LINUX_EDD_H
#define _LINUX_EDD_H
diff --git a/include/uapi/linux/edd.h b/include/uapi/linux/edd.h
index 0fe3e02aec65..bc4aaee451d9 100644
--- a/include/uapi/linux/edd.h
+++ b/include/uapi/linux/edd.h
@@ -10,13 +10,12 @@
* available at http://www.t13.org/docs2002/d1572r0.pdf. It is
* very similar to D1484 Revision 3 http://www.t13.org/docs2002/d1484r3.pdf
*
- * In a nutshell, arch/{i386,x86_64}/boot/setup.S populates a scratch
- * table in the boot_params that contains a list of BIOS-enumerated
- * boot devices.
- * In arch/{i386,x86_64}/kernel/setup.c, this information is
- * transferred into the edd structure, and in drivers/firmware/edd.c, that
- * information is used to identify BIOS boot disk. The code in setup.S
- * is very sensitive to the size of these structures.
+ * In a nutshell, arch/x86/boot/edd.c populates a scratch table in the
+ * boot_params that contains a list of BIOS-enumerated boot devices.
+ * In arch/x86/kernel/setup.c, this information is transferred into
+ * the edd structure, and in drivers/firmware/edd.c, that information
+ * is used to identify BIOS boot disk. The boot code is very sensitive
+ * to the size of these structures.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License v2.0 as published by
--
2.55.0
reply other threads:[~2026-07-13 21:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260713214503.34685-1-kuleshovmail@gmail.com \
--to=kuleshovmail@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox