All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-iio@vger.kernel.org>, <Michael.Hennerich@analog.com>,
	<lars@metafoo.de>, <knaack.h@gmx.de>, <pmeerw@pmeerw.net>
Subject: Re: [PATCH 1/2] staging:iio:ad7606: Remove incorrect kernel doc annotations
Date: Sun, 16 Sep 2018 12:19:12 +0100	[thread overview]
Message-ID: <20180916121912.096ab8db@archlinux> (raw)
In-Reply-To: <20180913110212.29068-1-alexandru.ardelean@analog.com>

On Thu, 13 Sep 2018 14:02:11 +0300
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:

> The ad7606_chip_info struct does not have the lock & name fields. Remove
> the kernel documentation annotations for it.
> 
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.

Thanks,

Jonathan

> ---
>  drivers/staging/iio/adc/ad7606.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/staging/iio/adc/ad7606.h b/drivers/staging/iio/adc/ad7606.h
> index 24c2a85f5c5a..57f11b46bc69 100644
> --- a/drivers/staging/iio/adc/ad7606.h
> +++ b/drivers/staging/iio/adc/ad7606.h
> @@ -11,10 +11,8 @@
>  
>  /**
>   * struct ad7606_chip_info - chip specific information
> - * @name:		identification string for chip
>   * @channels:		channel specification
>   * @num_channels:	number of channels
> - * @lock		protect sensor state
>   */
>  
>  struct ad7606_chip_info {

      parent reply	other threads:[~2018-09-16 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 11:02 [PATCH 1/2] staging:iio:ad7606: Remove incorrect kernel doc annotations Alexandru Ardelean
2018-09-13 11:02 ` [PATCH 2/2] staging:iio:ad7606: Add support for the ad7605-4 Alexandru Ardelean
2018-09-16 11:22   ` Jonathan Cameron
2018-09-17  7:33     ` Ardelean, Alexandru
2018-09-17  8:30       ` Jonathan Cameron
2018-09-17  9:01         ` Ardelean, Alexandru
2018-09-17 11:10           ` Jonathan Cameron
2018-09-22 15:35             ` Jonathan Cameron
2018-09-16 11:19 ` 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=20180916121912.096ab8db@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --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 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.