From: "tip-bot2 for Alexander Lobakin" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
Ingo Molnar <mingo@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/boot] scripts/head-object-list: Remove x86 from the list
Date: Mon, 09 Jan 2023 18:22:06 -0000 [thread overview]
Message-ID: <167328852698.4906.1342756515976813355.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230109170403.4117105-3-alexandr.lobakin@intel.com>
The following commit has been merged into the x86/boot branch of tip:
Commit-ID: 5353fff29e42d0efc844dcaf764336d20a7f6b44
Gitweb: https://git.kernel.org/tip/5353fff29e42d0efc844dcaf764336d20a7f6b44
Author: Alexander Lobakin <alexandr.lobakin@intel.com>
AuthorDate: Mon, 09 Jan 2023 18:04:03 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Mon, 09 Jan 2023 18:22:21 +01:00
scripts/head-object-list: Remove x86 from the list
Now that x86 boot code is not hardcoded to the particular linking
order, remove x86 files from the list and let them be placed inside
the vmlinux according only to the linker script and linker
preferences.
Signed-off-by: Alexander Lobakin <alexandr.lobakin@intel.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Tested-by: Jiri Slaby <jirislaby@kernel.org>
Link: https://lore.kernel.org/r/20230109170403.4117105-3-alexandr.lobakin@intel.com
---
scripts/head-object-list.txt | 6 ------
1 file changed, 6 deletions(-)
diff --git a/scripts/head-object-list.txt b/scripts/head-object-list.txt
index b074134..b2a0e21 100644
--- a/scripts/head-object-list.txt
+++ b/scripts/head-object-list.txt
@@ -42,10 +42,4 @@ arch/s390/kernel/head64.o
arch/sh/kernel/head_32.o
arch/sparc/kernel/head_32.o
arch/sparc/kernel/head_64.o
-arch/x86/kernel/head_32.o
-arch/x86/kernel/head_64.o
-arch/x86/kernel/head32.o
-arch/x86/kernel/head64.o
-arch/x86/kernel/ebda.o
-arch/x86/kernel/platform-quirks.o
arch/xtensa/kernel/head.o
next prev parent reply other threads:[~2023-01-09 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 17:04 [PATCH v3 0/2] x86/boot: fix relying on link order Alexander Lobakin
2023-01-09 17:04 ` [PATCH v3 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code Alexander Lobakin
2023-01-09 18:22 ` [tip: x86/boot] x86/boot: Robustify " tip-bot2 for Alexander Lobakin
2023-01-09 17:04 ` [PATCH v3 2/2] scripts/head-object-list: remove x86 from the list Alexander Lobakin
2023-01-09 18:22 ` tip-bot2 for Alexander Lobakin [this message]
2023-01-09 17:23 ` [PATCH v3 0/2] x86/boot: fix relying on link order Ingo Molnar
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=167328852698.4906.1342756515976813355.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=alexandr.lobakin@intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.