From: Viresh Kumar <viresh.kumar@linaro.org>
To: rob.herring@calxeda.com, grant.likely@secretlab.ca
Cc: spear-devel@list.st.com, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH] dt: add helper function to read u8 & u16 variables & arrays
Date: Thu, 25 Oct 2012 12:33:56 +0530 [thread overview]
Message-ID: <CAKohpom42SCMJ+=TdvAjqT0ibRugJi_gXkLy+49N6ExcRZqxLQ@mail.gmail.com> (raw)
In-Reply-To: <425b4bec021bce9a2de49959121907aeede6a0b9.1350064805.git.viresh.kumar@linaro.org>
On 12 October 2012 23:31, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> This adds following helper routines:
> - of_property_read_u8_array()
> - of_property_read_u16_array()
> - of_property_read_u8()
> - of_property_read_u16()
>
> First two actually share most of the code with of_property_read_u32_array(), so
> the common part is taken out into a macro, which can be used by all three
> *_array() routines.
Hi Rob,
Any comment here?
--
viresh
next prev parent reply other threads:[~2012-10-25 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 18:01 [PATCH] dt: add helper function to read u8 & u16 variables & arrays Viresh Kumar
2012-10-15 7:56 ` Shevchenko, Andriy
2012-10-15 8:06 ` Viresh Kumar
2012-10-25 7:03 ` Viresh Kumar [this message]
2012-10-25 13:19 ` Rob Herring
2012-10-25 14:18 ` Viresh Kumar
2012-10-26 4:17 ` Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2012-11-20 4:45 Viresh Kumar
2012-11-20 8:21 ` Shevchenko, Andriy
2012-11-20 8:25 ` Viresh Kumar
2012-11-20 17:21 ` Stephen Warren
[not found] ` <0ee5b74534a09d75c14b22c2d9330c4971ab30fb.1353386646.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-11-21 4:24 ` Rob Herring
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='CAKohpom42SCMJ+=TdvAjqT0ibRugJi_gXkLy+49N6ExcRZqxLQ@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=spear-devel@list.st.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).