From: Andrew Lunn <andrew@lunn.ch>
To: 최유호 <dbgh9129@gmail.com>
Cc: Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] ARM: devtree: Fix /cpus node reference leak
Date: Wed, 3 Jun 2026 05:09:41 +0200 [thread overview]
Message-ID: <b6764a7b-d288-486a-9feb-a7c6fa41d777@lunn.ch> (raw)
In-Reply-To: <CACrCO_WA27igaDzS5N_Vi3oxjSe3dvv8iLG3OLS_ZJ+NxTw4YQ@mail.gmail.com>
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
next prev parent reply other threads:[~2026-06-03 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 20:57 [PATCH v1] ARM: devtree: Fix /cpus node reference leak Yuho Choi
2026-06-03 2:54 ` 최유호
2026-06-03 3:09 ` Andrew Lunn [this message]
2026-06-03 15:33 ` 최유호
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6764a7b-d288-486a-9feb-a7c6fa41d777@lunn.ch \
--to=andrew@lunn.ch \
--cc=dbgh9129@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox