From: Dave Hansen <dave.hansen@intel.com>
To: Alexander Lobakin <alexandr.lobakin@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] x86/boot: fix relying on link order
Date: Tue, 8 Nov 2022 15:09:07 -0800 [thread overview]
Message-ID: <2993a60c-edaa-a29a-2644-3ee86c622847@intel.com> (raw)
In-Reply-To: <20221107125528.543764-1-alexandr.lobakin@intel.com>
On 11/7/22 04:55, Alexander Lobakin wrote:
> Ping?
>
> Also, I managed to remove .head.text at all from x86. Would it be
> better to respin this series with the third patch or send a
> follow-up later?
>
Hi Alexander,
Things are a bit busy in the review queue at the moment. As always,
we'd love help reviewing stuff. So, while you're waiting for us to
review this, could you perhaps look around and find a series that's also
hurting for review tags?
next prev parent reply other threads:[~2022-11-08 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:15 [PATCH v2 0/2] x86/boot: fix relying on link order Alexander Lobakin
2022-11-01 16:15 ` [PATCH v2 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code Alexander Lobakin
2022-11-02 6:14 ` Jiri Slaby
2022-11-01 16:15 ` [PATCH v2 2/2] scripts/head-object-list: remove x86 from the list Alexander Lobakin
2022-11-07 12:55 ` [PATCH v2 0/2] x86/boot: fix relying on link order Alexander Lobakin
2022-11-08 23:09 ` Dave Hansen [this message]
2022-11-21 12:09 ` Alexander Lobakin
2022-11-21 13:14 ` Borislav Petkov
2022-11-21 16:00 ` Alexander Lobakin
2022-12-07 15:08 ` Alexander Lobakin
2022-12-07 15:24 ` Borislav Petkov
2022-12-07 15:30 ` Alexander Lobakin
2022-12-07 15:52 ` Borislav Petkov
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=2993a60c-edaa-a29a-2644-3ee86c622847@intel.com \
--to=dave.hansen@intel.com \
--cc=alexandr.lobakin@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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 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.