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 72D1C31E107 for ; Mon, 2 Mar 2026 14:46:21 +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=1772462781; cv=none; b=fqMEhZLfLW6/NZ0aXUlKX9fCC6rRemV/lwMhkeJIMOaJOJHMrF3jUln6a9PrPgcziUu/gD0hcHCRh3+9qWcjz1utPCwsz1kOAZKz4jqKYggbuH+J0S0vXqwe6yK3UOQmerHaRYfSK0tGVyjfviksCdCTrfcAi4mpvmGSxBClvZ4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772462781; c=relaxed/simple; bh=m1vFph3OdU2InVKwuqLjx2hbi4olnyABK+OIwFM5rrs=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=NWUKTRcjzZyzI0dRWOFGrTw8naJ2Bs9CBs8jVhx2KfMe0lwGdGKdnOe2PTp0VI3D3WHkiTvwZsUrWyAAWOWIuU+2I9gPI0vEPPFiXXDLuAuqGIqPJuXyKK37AwbQMxSBpZuN1ATcN6+OfTip3YF/uOfkCWiq6EKb4vtdan3Vmuw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=r/sCJFaI; 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="r/sCJFaI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CFF46C2BC87; Mon, 2 Mar 2026 14:46:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772462781; bh=m1vFph3OdU2InVKwuqLjx2hbi4olnyABK+OIwFM5rrs=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=r/sCJFaIGbpNGX+Hg9IcWeea6/9YRLmXcuJ8RBXsGNhyAKotavjQ/lcTkn9ZA3CNS znjigIM1owzvVaOsd3sCc2IgDVG6oQlKhFW7cw0DuQCKtiDa9I4b5UCbDPZOzvap6e jsWU6USqc8eoU3q4i3xiTuriQjrCgFlvVeLEyyiKnuJoYqXdIIo4t9D6WbNvqeDlJa Dzzm+vWFjIRk4xazyJXjbu29vzt0HELppGqag6xuanHtU+vXqRIUvTSjHZZyL5HyIv v0lwM+ECbNykfcFS2DBweAYosKKoJcbeQywEzobiIQOxwhyOrFockUBV+GdPBJPvjS dhx88c2b1BIXw== From: Mark Brown To: Liam Girdwood , Matthias Brugger , AngeloGioacchino Del Regno , Felix Gu Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org In-Reply-To: <20260223-mt6363-v1-1-c99a2e8ac621@gmail.com> References: <20260223-mt6363-v1-1-c99a2e8ac621@gmail.com> Subject: Re: [PATCH] regulator: mt6363: Fix incorrect and redundant IRQ disposal in probe Message-Id: <177246277958.202807.7465555858082044279.b4-ty@kernel.org> Date: Mon, 02 Mar 2026 14:46:19 +0000 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="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-38bf1 On Mon, 23 Feb 2026 02:24:34 +0800, Felix Gu wrote: > In mt6363_regulator_probe(), devm_add_action_or_reset() is used to > automatically dispose of the IRQ mapping if the probe fails or the > device is removed. > > The manual call to irq_dispose_mapping() in the error path was redundant > as the reset action already triggers mt6363_irq_remove(). Furthermore, > the manual call incorrectly passed the hardware IRQ number (info->hwirq) > instead of the virtual IRQ mapping (info->virq). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: mt6363: Fix incorrect and redundant IRQ disposal in probe commit: 23942b71f07cc99e39d9216a5b370df494759d8c All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark