From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/config: Make the x86 defconfigs a bit more usable
Date: Thu, 24 Mar 2022 11:18:33 +0100 [thread overview]
Message-ID: <20220324101833.GD8939@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <164811181676.389.2059677983505845292.tip-bot2@tip-bot2>
On Thu, Mar 24, 2022 at 08:50:16AM -0000, tip-bot2 for Ingo Molnar wrote:
> The following commit has been merged into the x86/urgent branch of tip:
>
> Commit-ID: aee8bf2d5aab5e7cc24fa90238930fd14d72e580
> Gitweb: https://git.kernel.org/tip/aee8bf2d5aab5e7cc24fa90238930fd14d72e580
> Author: Ingo Molnar <mingo@kernel.org>
> AuthorDate: Thu, 24 Mar 2022 09:31:13 +01:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Thu, 24 Mar 2022 09:32:20 +01:00
>
> x86/config: Make the x86 defconfigs a bit more usable
>
> - Use 'make savedefconfig' to refresh & regenerate the files
> - Add in KVM boot enablers
We shouldn't duplicate kvm_guest.config.
> - Enable the cgroup features most distros rely on
I've not yet had defconfig+kvm_guest.config fail to boot on debian
images (I occasionally grab one here:
https://cloud.debian.org/images/cloud/sid/daily/latest/ )
next prev parent reply other threads:[~2022-03-24 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6PkRPjnHE@gmail.com>
2022-03-24 8:50 ` [tip: x86/urgent] x86/config: Make the x86 defconfigs a bit more usable tip-bot2 for Ingo Molnar
2022-03-24 10:18 ` Peter Zijlstra [this message]
2022-03-27 19:08 ` Ingo Molnar
2022-03-28 8:01 ` Peter Zijlstra
2022-03-27 19:08 ` tip-bot2 for 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=20220324101833.GD8939@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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