From: David Miller <davem@davemloft.net>
To: npalix@diku.dk
Cc: wli@holomorphy.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
julia@diku.dk
Subject: Re: [PATCH linux-next] sparc: Add missing of_node_put
Date: Wed, 03 Dec 2008 21:11:52 -0800 (PST) [thread overview]
Message-ID: <20081203.211152.263373582.davem@davemloft.net> (raw)
In-Reply-To: <200812021130.06197.npalix@diku.dk>
From: Nicolas Palix <npalix@diku.dk>
Date: Tue, 2 Dec 2008 11:30:06 +0100
>
> of_node_put is needed before discarding a value received from
> of_find_node_by_name, eg in error handling code or when the device
> node is no longer used.
Applied to sparc-next-2.6, thanks.
I'm not going to add this to sparc-2.6 or stable, it doesn't
fix any real bugs on sparc (no hot plugged OF nodes, ever)
and adding it to sparc-2.6 would potentitally create some
difficult conflicts in sparc-next-2.6 since we're just finishing
a full merge of arch/sparc64 into arch/sparc there.
prev parent reply other threads:[~2008-12-04 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 10:30 Nicolas Palix
2008-12-04 5:11 ` David Miller [this message]
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=20081203.211152.263373582.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix@diku.dk \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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
Powered by JetHome