linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Sören Brinkmann" <soeren.brinkmann@gmail.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ad7606_core: Fix checkpatch warning
Date: Sun, 31 Aug 2014 11:40:10 +0100	[thread overview]
Message-ID: <5402FB8A.8010905@kernel.org> (raw)
In-Reply-To: <1409468254-5312-1-git-send-email-soeren.brinkmann@gmail.com>

On 31/08/14 07:57, Sören Brinkmann wrote:
> Fix the checkpatch complaint regarding unnecessary line continuation.
>   WARNING: Avoid unnecessary line continuations
>   #143: FILE: ad7606_core.c:143:
> 
> Signed-off-by: Sören Brinkmann <soeren.brinkmann@gmail.com>
Applied to the togreg branch of iio.git.  Initially pushed out as testing for the
autobuilders to play.

Thanks,

Jonathan
> ---
>  drivers/staging/iio/adc/ad7606_core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/adc/ad7606_core.c b/drivers/staging/iio/adc/ad7606_core.c
> index f0f05f195d2c..bf2c8013134c 100644
> --- a/drivers/staging/iio/adc/ad7606_core.c
> +++ b/drivers/staging/iio/adc/ad7606_core.c
> @@ -140,7 +140,7 @@ static ssize_t ad7606_store_range(struct device *dev,
>  	return count;
>  }
>  
> -static IIO_DEVICE_ATTR(in_voltage_range, S_IRUGO | S_IWUSR, \
> +static IIO_DEVICE_ATTR(in_voltage_range, S_IRUGO | S_IWUSR,
>  		       ad7606_show_range, ad7606_store_range, 0);
>  static IIO_CONST_ATTR(in_voltage_range_available, "5000 10000");
>  
> 

      reply	other threads:[~2014-08-31 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31  6:57 [PATCH] staging: ad7606_core: Fix checkpatch warning Sören Brinkmann
2014-08-31 10:40 ` Jonathan Cameron [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=5402FB8A.8010905@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=soeren.brinkmann@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 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).