All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: will@kernel.org, Huang Shijie <shijie@os.amperecomputing.com>
Cc: patches@amperecomputing.com, cl@linux.com,
	Shubhang@os.amperecomputing.com,
	linux-arm-kernel@lists.infradead.org,
	krzysztof.kozlowski@linaro.org, geert+renesas@glider.be,
	arnd@arndb.de, linux-kernel@vger.kernel.org,
	peterz@infradead.org, soc@lists.linux.dev,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v2] arm64: defconfig: Remove the redundant SCHED_MC/SCHED_SMT
Date: Mon, 24 Nov 2025 15:16:35 +0000	[thread overview]
Message-ID: <aSR206S6V3-EaDfp@arm.com> (raw)
In-Reply-To: <176357945539.2095097.9737276524353571173.b4-ty@arm.com>

On Wed, Nov 19, 2025 at 07:10:55PM +0000, Catalin Marinas wrote:
> From: Catalin Marinas <catalin.marinas@arm.com>
> 
> On Tue, 21 Oct 2025 15:57:04 +0800, Huang Shijie wrote:
> > The patch "7bd291abe2d sched: Unify the SCHED_{SMT,CLUSTER,MC} Kconfig"
> > has enabled the SCHED_MC/SCHED_SMT by default for arm64.
> > 
> > So remove the redundant code in defconfig.
> 
> It's usually Arnd picking up defconfig changes but since it's more about
> core features, I queued it.
> 
> Applied to arm64 (for-next/defconfig), thanks!
> 
> [1/1] arm64: defconfig: Remove the redundant SCHED_MC/SCHED_SMT
>       https://git.kernel.org/arm64/c/a086f211a3b1

I'll drop this as Arnd already merged it.

-- 
Catalin


  reply	other threads:[~2025-11-24 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21  7:57 [PATCH v2] arm64: defconfig: Remove the redundant SCHED_MC/SCHED_SMT Huang Shijie
2025-10-21  8:04 ` Shijie Huang
2025-11-19 19:10 ` Catalin Marinas
2025-11-24 15:16   ` Catalin Marinas [this message]
2025-11-21 20:50 ` patchwork-bot+linux-soc

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=aSR206S6V3-EaDfp@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Shubhang@os.amperecomputing.com \
    --cc=arnd@arndb.de \
    --cc=cl@linux.com \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@amperecomputing.com \
    --cc=peterz@infradead.org \
    --cc=shijie@os.amperecomputing.com \
    --cc=soc@lists.linux.dev \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.com \
    /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.