From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from stravinsky.debian.org (stravinsky.debian.org [82.195.75.108]) (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 7CE4C3DBD76 for ; Mon, 20 Apr 2026 14:37:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=82.195.75.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776695854; cv=none; b=HodU1UA7kGokO7oFuP9w5ajcyh3jisQkA9WLr3xnCUyx3OiTNPdoG0UD3R62r8GPHRbfgstckJE713V8ghcQmWN18DF1In6rKHltXKE65BZY3T/IrGBSUqpwx+8EXLomlOe2a0VvHIo1g6thSb8xFRBP+Zxd2m4O2znl3223vog= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776695854; c=relaxed/simple; bh=VnlkNSCmjBdcpmwNyc8GeIFciUhmZ5OjT8wXGxSQm54=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=SKrXgZtGOlvY+ST1LTTmdL+tKEs3i0MNj8izuQ4fSYYmzww2CTKoF9YYKov4fsUfsddNXNnlUZHYp7ibddHStDJuFzd+X0SDOLuOd+Q2iNza+d88DxYm357IBz80r7QFmyN7zWBU+Aop3zvJR4N22SY1MGn3P77ePjQbfvUOlqE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org; spf=none smtp.mailfrom=debian.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b=EEmzCfCv; arc=none smtp.client-ip=82.195.75.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=debian.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b="EEmzCfCv" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=VnlkNSCmjBdcpmwNyc8GeIFciUhmZ5OjT8wXGxSQm54=; b=EEmzCfCvEsxW/AZAWePnCi/ZqS yEp0H5pXBi70SruNlG6gGDrhQGSJUMpAWLWX3Sy8WAUpsgtWHZ5oMQPTFyFevt0ZZrAUdcw5CAVm1 wke8yeEtovoCtKLtg+xv6qwZhBT7t+4U5GAG7raGQ0P6j+QDuW4itX1cnLeKyBGbWgpIAEd2uyD+u RJIrO9/wnN0rRUzY/JMq4jHkFHrZhFH3DnJ8Iv16FjP/NnAFi8EpQVqvQHRKqN1QvwsE5HlD1MdqU rCv27T6dVIcxtLi3coum9Z59jExT3hqh5T4Mk9vMyUC0Evj4Je6k40Hn991iQ3deFXAcyAS60i3wI dR7NQl9w==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1wEpkb-0009Rh-0z; Mon, 20 Apr 2026 14:37:25 +0000 Date: Mon, 20 Apr 2026 07:37:20 -0700 From: Breno Leitao To: Mark Rutland Cc: Catalin Marinas , Will Deacon , leo.bras@arm.com, leo.yan@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, palmer@dabbelt.com, paulmck@kernel.org, puranjay@kernel.org, usama.arif@linux.dev, kernel-team@meta.com Subject: Re: [PATCH RFC] arm64/irqflags: force inline of arch_local_irq_enable() Message-ID: References: <20260420-arm64_always_inline-v1-1-dba919cf46bc@debian.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Debian-User: leitao On Mon, Apr 20, 2026 at 03:14:49PM +0100, Mark Rutland wrote: > On Mon, Apr 20, 2026 at 06:15:24AM -0700, Breno Leitao wrote: > > On Mon, Apr 20, 2026 at 02:06:23PM +0100, Mark Rutland wrote: > > > > > > Are you happy to try that? > > > > Absolutely, I'll work on testing it that and put together a patch > > addressing all of them. > > > > Should this be targeted for stable backports as well? If so, which > > commit should I reference in the Fixes tag? > > I don't think we need to worry about backporting, and can do this as a > cleanup for now unless someone shouts that they're seeing brokenness in > a stable kernel. > > There's no specific commit for a fixes tag; this has always been a bit > dodgy, but we've evidently been getting away with it in practice. Ack. I'll run this through production testing for approximately 24 hours, then submit the patch. Thanks, --breno