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 969C32D6611 for ; Tue, 13 Jan 2026 20:20:06 +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=1768335606; cv=none; b=dummOvnI3h0oZQtU20bror/YQZhoJdhk7TfayX0msxPopHDzk0cXcSNE+UBjpqwsfH1ijQRE4pWWZXoguB4BNQjcor1TRjT1uHeHnrk47RCisMhLaKTazf7zZiWEv3/6GoQjboWoj0ihZx/iz3ZSR/fv2we5lVMVzVAjoXr0ePg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768335606; c=relaxed/simple; bh=iZuyblSJxNIMDzb0bKWUo66uFhRGHaPEd+5TwSZT4E4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=tmL7wQZ037F1+0XhpLn2oW8W904wWVcQbVEvrfw8VG1vR2ApTIozrO0tpRdzpotzHQaoD0a/VQX26nAYOz1OAmBEW08IduwbIbxA9JMatTBZHr9J5dXqLiE8+jTjC8qGqtzVEbD3hm6aY0N/8ePA3ict0A3cMvZCpZH/tL0c3Ps= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LVG2eeF4; 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="LVG2eeF4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 59B92C116C6; Tue, 13 Jan 2026 20:20:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768335606; bh=iZuyblSJxNIMDzb0bKWUo66uFhRGHaPEd+5TwSZT4E4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=LVG2eeF46IO50+IfgfqjCdqHSRUOro6QFylfwergZvUxOor1nuloi6s1mKru4OdUS av0Uoi56OLdt3I9yLjAvXvOH0iK40/tICOXfI1rfJ4Dp25o85gJTguVmeIRoGsD5Hw AVlNHlxGJImTzm8XXDJ3PcjGmEOIYT8IDSEL23K8A/DQFisb/M/YNhg3ZHCzEMWA8S IUNQ6vzxIQkaf+ZqjRbcTiA+VCUPt5APLsUzVj+IV9iz3PJok/s9947pRf5NtLNOYg E0v4FEVNRumin8NsaKmXglpJBTSBeGC17odzHCv4E1ZcuL9y/R/s7MrRK/xFYhRZ9j iYfy1xtiJh04w== From: Thomas Gleixner To: Vladimir Oltean Cc: Ioana Ciornei , Alexander Stein , Ulf Hansson , Geert Uytterhoeven , Johan Hovold , "Rafael J. Wysocki" , "Rob Herring (Arm)" , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/2] irqchip: convert ls-extirq to a platform driver In-Reply-To: <20260113184357.xwtlnp6ya3ujrhn3@skbuf> References: <20251205155735.2366732-1-ioana.ciornei@nxp.com> <87y0m1iclb.ffs@tglx> <20260113184357.xwtlnp6ya3ujrhn3@skbuf> Date: Tue, 13 Jan 2026 21:20:02 +0100 Message-ID: <87pl7di7t9.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, Jan 13 2026 at 20:43, Vladimir Oltean wrote: > On Tue, Jan 13, 2026 at 07:36:48PM +0100, Thomas Gleixner wrote: >> Yes. I've marked it "wait for update" and that's the state since >> Dec. 5th. > > Thanks for the response. I've since looked at the code, and Alexander's > cleanups are more than "nice", they are required, because when you > convert a driver from IRQCHIP_DECLARE() to platform_driver, you > introduce the possibility for it to be unbound from the device, and when > you do that, the memory that ls_extirq_probe() has allocated needs to be > freed. Oh, didn't look in that detail. Thanks for catching it! > Ioana, Alexander, could you please start a discussion to see who can > submit the follow up to this thread? Yes please.