From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
marmarek@invisiblethingslab.com, Juergen Gross <jgross@suse.com>,
Mike Rapoport <rppt@linux.ibm.com>,
x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/setup: Call early_reserve_memory() earlier
Date: Mon, 20 Sep 2021 20:59:40 -0700 [thread overview]
Message-ID: <YUlYrLG4rLwWw1ge@archlinux-ax161> (raw)
In-Reply-To: <YUlTlsVB7gJUVNT0@zn.tnic>
On Tue, Sep 21, 2021 at 05:38:40AM +0200, Borislav Petkov wrote:
> On Mon, Sep 20, 2021 at 03:48:18PM -0700, Nathan Chancellor wrote:
> > Could auto-latest get updated too so that it does not show up in -next?
> > I just spent a solid chunk of my day bisecting a boot failure on one of
> > my test boxes on -next down to this change, only to find out it was
> > already reported :/
>
> Sorry about that - commit is zapped from tip/master and tip/auto-latest.
Thank you!
> But your effort hasn't been in vain - you have a box which triggers this
> boot issue and I haven't found one yet.
>
> Can you please test on that exact test box whether the new version of
> that commit works?
>
> That one:
>
> https://lkml.kernel.org/r/20210920120421.29276-1-jgross@suse.com
>
> It would be much appreciated.
Sure thing. I tested both of my test systems and added a tested-by tag
to that thread. Glad to hear it was not in vain :)
Cheers,
Nathan
next prev parent reply other threads:[~2021-09-21 3:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 9:41 [PATCH] x86/setup: call early_reserve_memory() earlier Juergen Gross
2021-09-14 10:03 ` Jan Beulich
2021-09-14 11:06 ` Juergen Gross
2021-09-15 11:00 ` Borislav Petkov
2021-09-16 9:09 ` Mike Rapoport
2021-09-16 10:29 ` Borislav Petkov
2021-09-16 10:31 ` Juergen Gross
2021-09-14 10:49 ` Marek Marczykowski-Górecki
2021-09-16 10:50 ` [tip: x86/urgent] x86/setup: Call " tip-bot2 for Juergen Gross
2021-09-19 16:55 ` Mike Galbraith
2021-09-19 17:04 ` Mike Rapoport
2021-09-20 0:56 ` Mike Galbraith
2021-09-20 9:26 ` Mike Rapoport
2021-09-20 9:38 ` Borislav Petkov
2021-09-20 11:25 ` Mike Galbraith
2021-09-20 11:33 ` Juergen Gross
2021-09-19 17:15 ` Borislav Petkov
2021-09-20 6:00 ` Juergen Gross
2021-09-20 9:46 ` Mike Rapoport
2021-09-20 22:48 ` Nathan Chancellor
2021-09-21 3:38 ` Borislav Petkov
2021-09-21 3:59 ` Nathan Chancellor [this message]
2021-09-21 7:36 ` Borislav Petkov
2021-09-20 12:04 [PATCH v2] x86/setup: call " Juergen Gross
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
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=YUlYrLG4rLwWw1ge@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=efault@gmx.de \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--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.