public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com
Subject: Re: [PATCH v4 1/7] staging: iio: ad5933: change multi-line comment style
Date: Sat, 16 Mar 2019 18:34:58 +0000	[thread overview]
Message-ID: <20190316183458.1cdddb28@archlinux> (raw)
In-Reply-To: <20190316150618.7g6hxbmadvxe623o@smtp.gmail.com>

On Sat, 16 Mar 2019 12:06:18 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:

> Make multi-line comments compliant with the preferred code style.
> 
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to hopefully ignore.

Thanks,

Jonathan

> ---
>  drivers/staging/iio/impedance-analyzer/ad5933.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c
> index 3134295f014f..05e2185bfdae 100644
> --- a/drivers/staging/iio/impedance-analyzer/ad5933.c
> +++ b/drivers/staging/iio/impedance-analyzer/ad5933.c
> @@ -474,7 +474,8 @@ static IIO_DEVICE_ATTR(out_voltage0_settling_cycles, 0644,
>  			ad5933_store,
>  			AD5933_OUT_SETTLING_CYCLES);
>  
> -/* note:
> +/*
> + * note:
>   * ideally we would handle the scale attributes via the iio_info
>   * (read|write)_raw methods, however this part is a untypical since we
>   * don't create dedicated sysfs channel attributes for out0 and in0.
> @@ -572,7 +573,8 @@ static int ad5933_ring_postenable(struct iio_dev *indio_dev)
>  {
>  	struct ad5933_state *st = iio_priv(indio_dev);
>  
> -	/* AD5933_CTRL_INIT_START_FREQ:
> +	/*
> +	 * AD5933_CTRL_INIT_START_FREQ:
>  	 * High Q complex circuits require a long time to reach steady state.
>  	 * To facilitate the measurement of such impedances, this mode allows
>  	 * the user full control of the settling time requirement before
> @@ -663,7 +665,8 @@ static void ad5933_work(struct work_struct *work)
>  	}
>  
>  	if (status & AD5933_STAT_SWEEP_DONE) {
> -		/* last sample received - power down do
> +		/*
> +		 * last sample received - power down do
>  		 * nothing until the ring enable is toggled
>  		 */
>  		ad5933_cmd(st, AD5933_CTRL_POWER_DOWN);


      reply	other threads:[~2019-03-16 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 15:06 [PATCH v4 1/7] staging: iio: ad5933: change multi-line comment style Marcelo Schmitt
2019-03-16 18:34 ` 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=20190316183458.1cdddb28@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=kernel-usp@googlegroups.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=pmeerw@pmeerw.net \
    /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