From: Borislav Petkov <bp@alien8.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Juergen Gross <jgross@suse.com>,
John Dorminy <jdorminy@redhat.com>,
anjaneya.chagam@intel.com, dan.j.williams@intel.com,
Hugh Dickins <hughd@google.com>,
"Patrick J. Volkerding" <volkerdi@gmail.com>
Subject: [PATCH 0/3] x86: Fix boot ordering issues yet again
Date: Mon, 13 Dec 2021 12:27:54 +0100 [thread overview]
Message-ID: <20211213112757.2612-1-bp@alien8.de> (raw)
In-Reply-To: <YbcTgQdTpJAHAZw4@zn.tnic>
From: Borislav Petkov <bp@suse.de>
Hi,
here are the three I'm going to queue this week. Thanks again to
everyone for the quick testing.
Borislav Petkov (2):
Revert "x86/boot: Mark prepare_command_line() __init"
Revert "x86/boot: Pull up cmdline preparation and early param parsing"
Mike Rapoport (1):
x86/boot: Move EFI range reservation after cmdline parsing
arch/x86/kernel/setup.c | 72 +++++++++++++++++------------------------
1 file changed, 30 insertions(+), 42 deletions(-)
--
2.29.2
next prev parent reply other threads:[~2021-12-13 11:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:04 [PATCH v2] x86/setup: call early_reserve_memory() earlier Juergen Gross
2021-09-21 0:01 ` Marek Marczykowski-Górecki
2021-09-21 3:59 ` Nathan Chancellor
2021-09-22 17:18 ` [tip: x86/urgent] x86/setup: Call " tip-bot2 for Juergen Gross
2021-11-04 5:38 ` Williams, Dan J
2021-11-04 11:40 ` Borislav Petkov
2021-11-04 17:36 ` Dan Williams
2021-11-15 11:36 ` [tip: x86/urgent] x86/boot: Pull up cmdline preparation and early param parsing tip-bot2 for Borislav Petkov
2021-12-09 14:38 ` John Dorminy
2021-12-09 15:19 ` Borislav Petkov
2021-12-09 15:26 ` Juergen Gross
2021-12-09 15:28 ` Borislav Petkov
2021-12-09 16:29 ` Mike Rapoport
2021-12-09 16:37 ` Borislav Petkov
2021-12-10 11:28 ` Borislav Petkov
2021-12-10 20:11 ` Hugh Dickins
2021-12-11 10:14 ` Borislav Petkov
2021-12-10 20:32 ` Patrick J. Volkerding
2021-12-11 10:29 ` Borislav Petkov
2021-12-11 5:24 ` John Dorminy
2021-12-11 10:30 ` Borislav Petkov
2021-12-13 8:20 ` Mike Rapoport
2021-12-13 9:33 ` Borislav Petkov
2021-12-13 11:27 ` Borislav Petkov [this message]
2021-12-13 11:27 ` [PATCH 1/3] Revert "x86/boot: Mark prepare_command_line() __init" Borislav Petkov
2021-12-15 13:05 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
2021-12-13 11:27 ` [PATCH 2/3] Revert "x86/boot: Pull up cmdline preparation and early param parsing" Borislav Petkov
2021-12-15 13:05 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
2021-12-13 11:27 ` [PATCH 3/3] x86/boot: Move EFI range reservation after cmdline parsing Borislav Petkov
2021-12-15 13:12 ` [tip: x86/urgent] " tip-bot2 for Mike Rapoport
[not found] ` <CANGBn69pGb-nscv8tXN1UKDEQGEMWRKuPVPLgg+q2m7V_sBvHw@mail.gmail.com>
2021-12-20 18:49 ` [tip: x86/urgent] x86/boot: Pull up cmdline preparation and early param parsing Patrick J. Volkerding
2021-12-20 18:59 ` Borislav Petkov
2021-12-20 19:08 ` Borislav Petkov
2021-12-09 15:49 ` John Dorminy
2021-12-09 16:07 ` Borislav Petkov
2021-12-15 13:05 ` [tip: x86/urgent] x86/boot: Move EFI range reservation after cmdline parsing tip-bot2 for Mike Rapoport
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=20211213112757.2612-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=anjaneya.chagam@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hughd@google.com \
--cc=jdorminy@redhat.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=volkerdi@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).