From: Christoph Fritz <chf.fritz@googlemail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
linux-can@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Andreas Larsson <andreas@gaisler.com>,
"Hans J. Koch" <hjk@hansjkoch.de>,
Bill Pemberton <wfp5p@virginia.edu>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH v2] can: sja1000: fix endian on arm
Date: Thu, 11 Apr 2013 20:53:33 +0200 [thread overview]
Message-ID: <1365706413.4136.15.camel@mars> (raw)
In-Reply-To: <51670532.5060101@pengutronix.de>
On Thu, 2013-04-11 at 20:47 +0200, Marc Kleine-Budde wrote:
> On 04/11/2013 08:44 PM, Christoph Fritz wrote:
> > To get correct endian on arm cpus while reading device tree properties,
> > this patch replaces of_get_property() with of_property_read_u32().
> >
> > Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
>
> looks good, one nitpick inline
>
> > ---
> > drivers/net/can/sja1000/sja1000_of_platform.c | 32 ++++++++++++-------------
> > 1 file changed, 16 insertions(+), 16 deletions(-)
> >
> > diff --git a/drivers/net/can/sja1000/sja1000_of_platform.c b/drivers/net/can/sja1000/sja1000_of_platform.c
> > @@ -168,8 +168,8 @@ static int sja1000_ofp_probe(struct platform_device *ofdev)
> > priv->cdr |= CDR_CLK_OFF; /* default */
> > }
> >
> > - prop = of_get_property(np, "nxp,no-comparator-bypass", NULL);
> > - if (!prop)
> > + err = of_property_read_u32(np, "nxp,no-comparator-bypass", &prop);
>
> What about using of_property_read_bool instead?
Yeah, that would be better, thanks - let me re-roll this.
next prev parent reply other threads:[~2013-04-11 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 13:48 [PATCH] can: sja1000: use cpu endian Christoph Fritz
2013-04-08 13:57 ` Marc Kleine-Budde
2013-04-11 18:44 ` [PATCH v2] can: sja1000: fix endian on arm Christoph Fritz
2013-04-11 18:47 ` Marc Kleine-Budde
2013-04-11 18:53 ` Christoph Fritz [this message]
2013-04-11 19:14 ` [PATCH v3] " Christoph Fritz
2013-04-11 19:21 ` Marc Kleine-Budde
2013-04-11 19:32 ` [PATCH v4] " Christoph Fritz
2013-04-11 19:38 ` Marc Kleine-Budde
2013-04-12 11:18 ` Marc Kleine-Budde
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=1365706413.4136.15.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=andreas@gaisler.com \
--cc=daniel@zonque.org \
--cc=grant.likely@secretlab.ca \
--cc=hjk@hansjkoch.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=wfp5p@virginia.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.