All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>,
	linux-bcachefs@vger.kernel.org
Subject: [ktest PATCH] kconfig: stop requiring CONFIG_MCORE2
Date: Tue,  1 Apr 2025 20:30:10 -0700	[thread overview]
Message-ID: <20250402033010.266607-1-ebiggers@kernel.org> (raw)

From: Eric Biggers <ebiggers@google.com>

This was removed upstream.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 tests/kconfig.sh | 2 --
 1 file changed, 2 deletions(-)

diff --git a/tests/kconfig.sh b/tests/kconfig.sh
index f3fb18f..5254530 100644
--- a/tests/kconfig.sh
+++ b/tests/kconfig.sh
@@ -5,11 +5,10 @@ have_virtio=0
 have_suspend=0
 
 case $ktest_arch in
     x86)
 	require-kernel-config SMP
-	require-kernel-config MCORE2	# optimize for core2
 	require-kernel-config IO_DELAY_0XED
 	require-kernel-config 64BIT=n
 	require-kernel-config ACPI	# way slower without it, do not know why
 	require-kernel-config UNWINDER_ORC
 	require-kernel-config HARDLOCKUP_DETECTOR
@@ -21,11 +20,10 @@ case $ktest_arch in
 
 	require-kernel-append console=hvc0
 	;;
     x86_64)
 	require-kernel-config SMP
-	require-kernel-config MCORE2	# optimize for core2
 	require-kernel-config IO_DELAY_0XED
 	#require-kernel-config IA32_EMULATION
 	require-kernel-config 64BIT
 	require-kernel-config ACPI	# way slower without it, do not know why
 	require-kernel-config UNWINDER_ORC

base-commit: 53229b36f8c4df0690af64dedfce3e247334505e
-- 
2.49.0


             reply	other threads:[~2025-04-02  3:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  3:30 Eric Biggers [this message]
2025-04-02  3:43 ` [ktest PATCH] kconfig: stop requiring CONFIG_MCORE2 Kent Overstreet

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=20250402033010.266607-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.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.