From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Hui Wang <jason77.wang@gmail.com>
Cc: wg@grandegger.com, shawn.guo@linaro.org, linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/2] can: flexcan: use of_property_read_u32 to get DT entry value
Date: Sat, 30 Jun 2012 14:29:30 +0200 [thread overview]
Message-ID: <4FEEF12A.7010906@pengutronix.de> (raw)
In-Reply-To: <1340871695-26327-2-git-send-email-jason77.wang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On 06/28/2012 10:21 AM, Hui Wang wrote:
> of_property_read_u32() can auto handle endian problems, use this
> function can make code clean and simple.
>
> No need to check return value here since the following got value
> check will handle this.
>
> Cc: linux-can@vger.kernel.org
> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
> Cc: Wolfgang Grandegger <wg@grandegger.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Signed-off-by: Hui Wang <jason77.wang@gmail.com>
Applied to linux-can-next
tnx, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2012-06-30 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 8:21 [PATCH v2 0/2] can: flexcan: upgrade the flexcan.c to support i.MX6 Hui Wang
2012-06-28 8:21 ` [PATCH v2 1/2] can: flexcan: use of_property_read_u32 to get DT entry value Hui Wang
2012-06-28 8:21 ` [PATCH v2 2/2] can: flexcan: add hardware controller version support Hui Wang
2012-06-28 10:20 ` Marc Kleine-Budde
2012-06-28 10:22 ` [PATCH v2 1/2] can: flexcan: use of_property_read_u32 to get DT entry value Marc Kleine-Budde
2012-07-02 2:33 ` Hui Wang
2012-06-30 12:29 ` Marc Kleine-Budde [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=4FEEF12A.7010906@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=jason77.wang@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=wg@grandegger.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).