From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Mark Brown <broonie@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Driver core: Add accessor for device tree node
Date: Tue, 30 Jul 2013 06:57:20 -0700 [thread overview]
Message-ID: <20130730135720.GC27962@kroah.com> (raw)
In-Reply-To: <007601ce8d06$13dbb890$3b9329b0$@samsung.com>
On Tue, Jul 30, 2013 at 06:20:47PM +0900, Jingoo Han wrote:
> Add the wrapper function for retrieving device tree node instead of
> accessing dev->of_node directly.
Why?
next prev parent reply other threads:[~2013-07-30 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 9:20 [PATCH] Driver core: Add accessor for device tree node Jingoo Han
2013-07-30 13:57 ` Greg Kroah-Hartman [this message]
2013-07-31 0:47 ` Jingoo Han
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=20130730135720.GC27962@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).