From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: joseph daniel <josephdanielwalter@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/iio/meter: fix the coding style problem
Date: Tue, 01 May 2012 10:50:39 +0200 [thread overview]
Message-ID: <4F9FA3DF.9060603@metafoo.de> (raw)
In-Reply-To: <4F9F9711.1010904@cam.ac.uk>
On 05/01/2012 09:56 AM, Jonathan Cameron wrote:
> On 4/30/2012 9:01 PM, Lars-Peter Clausen wrote:
>> On 04/30/2012 09:26 PM, joseph daniel wrote:
>>> Signed-off-by: joseph daniel<josephdanielwalter@gmail.com>
>>> ---
>>> Hi Lars,
>>> Thanks for review. how about the below change?
>>> drivers/staging/iio/meter/ade7854-i2c.c | 6 +++++-
>>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/staging/iio/meter/ade7854-i2c.c
>>> b/drivers/staging/iio/meter/ade7854-i2c.c
>>> index 1e1faa0..52bdb05 100644
>>> --- a/drivers/staging/iio/meter/ade7854-i2c.c
>>> +++ b/drivers/staging/iio/meter/ade7854-i2c.c
>>> @@ -181,6 +181,7 @@ static int ade7854_i2c_read_reg_32(struct device
>>> *dev,
>>> {
>>> struct iio_dev *indio_dev = dev_get_drvdata(dev);
>>> struct ade7854_state *st = iio_priv(indio_dev);
>>> + uint32_t value;
>>> int ret;
>>>
>>> mutex_lock(&st->buf_lock);
>>> @@ -195,7 +196,10 @@ static int ade7854_i2c_read_reg_32(struct device
>>> *dev,
>>> if (ret)
>>> goto out;
>>>
>>> - *val = (st->rx[0]<< 24) | (st->rx[1]<< 16) | (st->rx[2]<< 8)
>>> | st->rx[3];
>>> + memcpy(&value, st->rx, sizeof(uint32_t));
>>> +
>> Uhm, yes, you are right st->rx is unaligned. The memcpy is not
>> necessary though
>> if you use get_unaligned_be32. Sorry for the pointer to the wrong
>> function.
> Or we could just force the alignment of st->rx? Might not be worth
> bothering.
Yes, but be32_to_cpu wants a be32 and there is another functions which only
does a 16 bit access on rx, so we'd need to cast and things get messy. Also for
tx we store first a 16bit value and then a 32bit value and while it is possible
to get this properly aligned this gets a bit messy too. I think we are fine
with {get,set}_unaligned for now.
next prev parent reply other threads:[~2012-05-01 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 19:26 [PATCH] staging/iio/meter: fix the coding style problem joseph daniel
2012-04-30 20:01 ` Lars-Peter Clausen
2012-05-01 4:08 ` joseph daniel
2012-05-01 4:08 ` joseph daniel
2012-05-01 7:56 ` Jonathan Cameron
2012-05-01 8:50 ` Lars-Peter Clausen [this message]
2012-04-30 20:04 ` Dan Carpenter
2012-04-30 20:18 ` Dan Carpenter
2012-05-01 4:09 ` joseph daniel
2012-05-01 4:09 ` joseph daniel
-- strict thread matches above, loose matches on Subject: below --
2012-04-30 18:21 joseph daniel
2012-04-30 18:32 ` Lars-Peter Clausen
2012-04-30 18:12 joseph daniel
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=4F9FA3DF.9060603@metafoo.de \
--to=lars@metafoo.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=josephdanielwalter@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=w.sang@pengutronix.de \
/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.