From: Jonathan Cameron <jic23@kernel.org>
To: Tolga Ceylan <tolga.ceylan@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Staging: iio: Coding style correction
Date: Sun, 08 Feb 2015 11:55:05 +0000 [thread overview]
Message-ID: <54D74E99.6080807@kernel.org> (raw)
In-Reply-To: <1423381233-11810-1-git-send-email-tolga.ceylan@gmail.com>
On 08/02/15 07:40, Tolga Ceylan wrote:
> Line over 80 characters corrected
>
> Signed-off-by: Tolga Ceylan <tolga.ceylan@gmail.com>
Applied, again with an amended patch title to reflect the driver
it is changing rather that simply the subsystem.
> ---
> drivers/staging/iio/meter/ade7854-i2c.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/meter/ade7854-i2c.c b/drivers/staging/iio/meter/ade7854-i2c.c
> index 5b33c7f..5d0671a 100644
> --- a/drivers/staging/iio/meter/ade7854-i2c.c
> +++ b/drivers/staging/iio/meter/ade7854-i2c.c
> @@ -195,7 +195,8 @@ 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];
> + *val = (st->rx[0] << 24) | (st->rx[1] << 16) |
> + (st->rx[2] << 8) | st->rx[3];
> out:
> mutex_unlock(&st->buf_lock);
> return ret;
>
next prev parent reply other threads:[~2015-02-08 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 7:40 [PATCH 1/1] Staging: iio: Coding style correction Tolga Ceylan
2015-02-08 7:40 ` Tolga Ceylan
2015-02-08 11:55 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-08 8:04 [PATCH 1/1] Staging: iio: Coding Style Correction Tolga Ceylan
2015-02-08 8:04 ` Tolga Ceylan
2015-02-08 11:52 ` Jonathan Cameron
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=54D74E99.6080807@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tolga.ceylan@gmail.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.