From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 8E6892F39B9 for ; Tue, 7 Apr 2026 21:08:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775596120; cv=none; b=Vr5sCatCVyO/6lStUOFUWMwa6bb1DqvtjiagmPM123gZrI1c5yEWkHgNpfL/kR1bP6I9GIuBGum1kw3lcZYZRaYz21ztxKC8Z7cuSvj3LEZmsK5MXswst+QJGr9Co8f0zgfnWkpovjC1GMpil5kuW6TBTki4oRI33EZwMOA2yLU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775596120; c=relaxed/simple; bh=gIIaaUV+7chBOO2TykQwm8KJUrCM1gtVUozq7g5UYi4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=OFd4CC0SU2ze2GdTmz4h5uTDaxn4LvyI9wPqY6gYK8ogQrnTckhfy4/6W73Ep0sL/L6j0dzxAdxqCTm7WU5CRWCdr5WmU83Hfjg8jRCx+K3gAs/wdm/UIB4q5uhK39ju1TEZAeDaE6px7/yLZ2GenR1qCir1gaoUrovGCn+TyDA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=m0mxOE+P; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="m0mxOE+P" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6EFEFC116C6; Tue, 7 Apr 2026 21:08:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775596120; bh=gIIaaUV+7chBOO2TykQwm8KJUrCM1gtVUozq7g5UYi4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=m0mxOE+P0p15xy5t+yMoKAbZL+g5VoESh66ptbVCBGkRr+88h2L8SrGP5dntdWWZl LfcjYKbo1NjpG4vFL8a1HhrowjPzYAI8JCYqELuune0oBSXwh2c/IIuYlAYpgEmLkz 6tnqGy5OB5JsAuDqQUlt4UoE/f7qXEQ3pgtimExTBvyCvjDJA/pssKjus1s6QDvD0h VusIAoOeuvq/2jQt3PL6rM4+8ly+FQHr3b28OLbtYuojG24F2eSkd6CgdLZbRPSFpJ g4mHEu7BFzSY74iY+0M97H2dTvhZjD32T+qVQXj6MFOYJGofcfllp2oC3SERO1HlIw Ta6HfAxRV7t4A== From: Thomas Gleixner To: Mark Rutland , linux-arm-kernel@lists.infradead.org, Andy Lutomirski , Catalin Marinas , Peter Zijlstra , Will Deacon Cc: ada.coupriediaz@arm.com, linux-kernel@vger.kernel.org, mark.rutland@arm.com, ruanjinjie@huawei.com, vladimir.murzin@arm.com Subject: Re: [PATCH 00/10] arm64/entry: In-Reply-To: <20260407131650.3813777-1-mark.rutland@arm.com> References: <20260407131650.3813777-1-mark.rutland@arm.com> Date: Tue, 07 Apr 2026 23:08:36 +0200 Message-ID: <87cy0a4gx7.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, Apr 07 2026 at 14:16, Mark Rutland wrote: > I've split the series into a prefix of changes for generic irqentry, > followed by changes to the arm64 code. I'm hoping that we can queue the > generic irqentry patches onto a stable branch, or take those via arm64. > The patches are as follows: > > * Patches 1 and 2 are cleanup to the generic irqentry code. These have no > functional impact, and I think these can be taken regardless of the > rest of the series. > > * Patches 3 to 5 refactor the generic irqentry code as described above, > providing separate irqentry_{enter,exit}() functions and providing a > split form of irqentry_exit_to_kernel_mode() similar to what exists > for irqentry_exit_to_user_mode(). These patches alone should have no > functional impact. I looked through them and I can't find any problem with them. I queued them localy and added the missing kernel doc as I promised you on IRC. As I have quite a conflict pending in the tip tree with other changes related to the generic entry code, I suggest that I queue 1-5, tag them for arm64 consumption and merge them into the conflicting branch to avoid trouble with pull request ordering and headaches for the -next people. Does that work for you? Thanks, tglx