linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 2/4] iio: humidity: hts221: remove trailing whitespace from a comment
Date: Sun, 14 Jan 2018 14:01:55 +0000	[thread overview]
Message-ID: <20180114140155.44512615@archlinux> (raw)
In-Reply-To: <20180108221231.13283-3-lorenzo.bianconi@redhat.com>

On Mon,  8 Jan 2018 23:12:29 +0100
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:

> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
I wonder when that one snuck in and why we haven't had
doesn't of static checker warnings about it.

Applied to the togreg branch of iio.git and pushed out
as testing for the autobuilders to play with it.

Thanks,

Jonathan

> ---
>  drivers/iio/humidity/hts221_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/humidity/hts221_buffer.c b/drivers/iio/humidity/hts221_buffer.c
> index e971ea425268..f9522ee62170 100644
> --- a/drivers/iio/humidity/hts221_buffer.c
> +++ b/drivers/iio/humidity/hts221_buffer.c
> @@ -61,7 +61,7 @@ static irqreturn_t hts221_trigger_handler_thread(int irq, void *private)
>  	if (err < 0)
>  		return IRQ_HANDLED;
>  
> -	/* 
> +	/*
>  	 * H_DA bit (humidity data available) is routed to DRDY line.
>  	 * Humidity sample is computed after temperature one.
>  	 * Here we can assume data channels are both available if H_DA bit


      reply	other threads:[~2018-01-14 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 22:12 [PATCH v3 2/4] iio: humidity: hts221: remove trailing whitespace from a comment Lorenzo Bianconi
2018-01-14 14:01 ` 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=20180114140155.44512615@archlinux \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.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).