From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from casper.infradead.org (casper.infradead.org [90.155.50.34])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id E373D23536B;
	Thu, 28 May 2026 10:27:06 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1779964031; cv=none; b=Kt5dMLITsgooepBo3NBikyKK+A1QjZOxFSZO+24HZD9r2JtTw1HskNTZIJ6zZ5w6FyFUdQsL6vMzw+AGuTwKYM+Tl7tFOHgE4oHEKsLTchSX5IJdefG1MlSSG70IMjJcCSXnZyTA9NoxkJ1lEZNOjd9XijKj4lftRWBuT17+NFo=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1779964031; c=relaxed/simple;
	bh=CnSMlLcN9YaG1pQTjw5ZuMkRn/mXcrt5ALR25Rthfdw=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=dZcsvICSyqwVZ4KDjKO/g/W58jeTHCx2GA7XC1oZcs0MefRevbyvFpXcbZOMaQm2su65vZvKxRUaRnLdd3BUqGbkrUKYiz6SuBHsji3G6j7WCW7Il8NHZ0iw8mCv3mw9UDKLeYVLcuRqpDBGoFQyPaur+nBK1Oi5m/8LXQoyfhM=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=LlxTQk+o; arc=none smtp.client-ip=90.155.50.34
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org
Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="LlxTQk+o"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version:
	References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:
	Content-Transfer-Encoding:Content-ID:Content-Description;
	bh=mUBLy2aWvOnDr9Z3uAXkA3OZMgBiEo35Lnv5l4749zo=; b=LlxTQk+oqjgBVNq4pF/TfehG7k
	QuMRJbdXxHHeCgGFGDelvMBkk8AtWiuIe88a2YVWHCNVXvk9Vc5wd0xRBdNZBwU8OGhxQxlm/w8Wb
	hM/ivKDG8GHfOkhDxgUT61hMk7QOfh9yCybbIgUFL6wnAQB7/lqWTzsVNvAA+TV1G4jzVpWnHvKi0
	64QIMZz8T4EEDlQ6mXt3ODfbelqGWhQD7ZQrpvl087EzfR3FMLNGQUYdYo5kC/tyIF2tWN7KQ2OyN
	W39UMmSycy5Wm5RcFfG8MbNYC4B9KLD5TdjdZonRUdSOQvmG2ZbHs5jwgfWZ5is1Z2zNDrVeOUc4F
	rFnfI/nA==;
Received: from 2001-1c00-8d85-4b00-266e-96ff-fe07-7dcc.cable.dynamic.v6.ziggo.nl ([2001:1c00:8d85:4b00:266e:96ff:fe07:7dcc] helo=noisy.programming.kicks-ass.net)
	by casper.infradead.org with esmtpsa (Exim 4.99.1 #2 (Red Hat Linux))
	id 1wSXxA-000000047Tp-0mFa;
	Thu, 28 May 2026 10:27:04 +0000
Received: by noisy.programming.kicks-ass.net (Postfix, from userid 1000)
	id 17F22300673; Thu, 28 May 2026 12:27:03 +0200 (CEST)
Date: Thu, 28 May 2026 12:27:03 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	Marco Elver <elver@google.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Bart Van Assche <bvanassche@acm.org>, x86@kernel.org,
	dlemoal@kernel.org
Subject: Re: [tip: locking/core] compiler-context-analysis: Bump required
 Clang version to 23
Message-ID: <20260528102703.GE343181@noisy.programming.kicks-ass.net>
References: <20260515124426.2227783-1-elver@google.com>
 <177926568868.711.3058599932884307249.tip-bot2@tip-bot2>
 <ahgHCly1VO0-p_ED@ryzen>
 <20260528093722.GD343181@noisy.programming.kicks-ass.net>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260528093722.GD343181@noisy.programming.kicks-ass.net>

On Thu, May 28, 2026 at 11:37:22AM +0200, Peter Zijlstra wrote:

> > Would it be possible for you to provide an immutable branch with only
> > this specific commit, such that I could merge that immutable branch to
> > libata/for-next (such that we carry the exact same SHA1) in both trees?
> 
> I think that means I have to rebase tip/locking/core; pull out that
> patch and stick it in a separate branch and then merge the two branches,
> right? Git and me never really get along well.
> 
> Let me see if I can do this without destroying stuff :-)

So I think I managed; there should now be tip/locking/context with just
the one commit in and tip/locking/core has an extra merge commit.

Bit ugly, but I've no idea if this can be done better.