From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (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 290AA20468E for ; Wed, 3 Jun 2026 03:09:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780456186; cv=none; b=onYU4tMd+n7Bvj3upd6hp6xm0Z97677ZYrHj2sFktfDuInTPz9i+3zNngCuDg65ATMncTkqjGhB2rfAmJbepNovvPGQmdxoO6lDtGJcG0C/okNHEQjlrcN/+WrpZhPahOx9Jq5zFUDH1j+h+2eZnh/Xy8peMbbm0+0nBEE/FbWY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780456186; c=relaxed/simple; bh=HX/Ra3gm9eNOHCWMu97I7lOI4sISg2nvt1eb6h897mU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ooes2ece2DbXN7MyIREYPDHnrqQvhX8MF1zbKiDcpL1oZtcQOIMvRxazrqX0zqJ49FFbajVpnJjftzV/1wMsXZcsXSl6sXfs8OoZ5emGYAC4duWl2cHsXypQA+4ZGX5eYqh/Axu6D7+5TEV5HMcUFZnZb+7il0H9fmPob11zLaQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=fzWpKg7b; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="fzWpKg7b" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition: In-Reply-To:References; bh=x0j4rLmtzrhLWc3rpCVeyKxG9qf7kIHCbWejuItKZMM=; b=fz WpKg7bQu8hQh1vAlENI5v0u5giorXinp8ibvnHTbE7sm1XkVVxiLvJqTocI0ARJuIUGzDb3NE84sT +RMLdVX17rRvgdjpNSh7nNR49ElW+pH8FaUz6Vg6iQWtaZ9ynnoATGZBv5X0GYqVuB2sL86+teP7z YHXzeoxzeX68SMA=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1wUbzB-005oYg-LU; Wed, 03 Jun 2026 05:09:41 +0200 Date: Wed, 3 Jun 2026 05:09:41 +0200 From: Andrew Lunn To: =?utf-8?B?7LWc7Jyg7Zi4?= Cc: Russell King , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1] ARM: devtree: Fix /cpus node reference leak Message-ID: References: <20260513205720.638900-1-dbgh9129@gmail.com> 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-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Tue, Jun 02, 2026 at 10:54:26PM -0400, 최유호 wrote: > Hi, > > Just a gentle reminder regarding this patch. > > I would appreciate any feedback when you have a chance to review it. You are more likely to get comments if you repost the patch. But please think about what you are fixing. Is it theoretical? Is it old code which has been running perfectly well for 10 years? Is it something really early in the boot that if it fails, the machine is dead anyway, so who cares about a minor resource leak? Are these patches actual worth while? Andrew