From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
rank Rowand <frowand.list@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Question] refcount of DT node
Date: Sun, 17 Apr 2016 00:02:54 +0900 [thread overview]
Message-ID: <CAK7LNAQiw4VT5Cs1KzXg_K6r8QjiPd8o9xo_oaix0DOXYosK=g@mail.gmail.com> (raw)
In-Reply-To: <20160414183855.GU19428@n2100.arm.linux.org.uk>
Hi experts.
2016-04-15 3:38 GMT+09:00 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>
> Their stance is not something I agree with - if we have something,
> it should be correct, even if it's not what we would ultimately
> desire, _or_ it should be removed. This half-way house that we
> have today is total madness to me.
I agree with Russell here.
I am comfortable to do my best in the given API at this point
(and also happy to adjust my drivers when a new API is supported in the future).
So, the answers from DT people are really helpful for me to write correct code.
Thank you everyone!
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-04-16 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 7:47 [Question] refcount of DT node Masahiro Yamada
2016-04-14 8:48 ` Russell King - ARM Linux
2016-04-14 9:59 ` Mark Rutland
2016-04-14 10:02 ` Pantelis Antoniou
2016-04-14 16:10 ` Frank Rowand
2016-04-14 17:02 ` Rob Herring
2016-04-14 18:38 ` Russell King - ARM Linux
2016-04-16 15:02 ` Masahiro Yamada [this message]
2016-04-14 10:10 ` Mark Rutland
2016-04-14 10:40 ` Pantelis Antoniou
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='CAK7LNAQiw4VT5Cs1KzXg_K6r8QjiPd8o9xo_oaix0DOXYosK=g@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
/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).