All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maxwell Doose" <maxwell@maxwelld.cc>
To: "Arnav Kapoor" <kapoorarnav43@gmail.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rodrigo Alencar" <rodrigo.alencar@analog.com>,
	<linux@analog.com>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: dac: ad5686: fix channels member name in kernel-doc
Date: Sun, 11 Oct 2026 10:09:30 -0500	[thread overview]
Message-ID: <DM23RGDMAP30.4KFLP01K5LSM@maxwelld.cc> (raw)
In-Reply-To: <20261011045149.353929-1-kapoorarnav43@gmail.com>

On Sat Oct 10, 2026 at 11:51 PM CDT
Arnav Kapoor <kapoorarnav43@gmail.com> wrote:

> The kernel-doc for struct ad5686_chip_info describes a member called
> @channel, but the member is named channels. W=1 builds report:
>
>   Warning: drivers/iio/dac/ad5686.h:95 struct member 'channels' not
>   described in 'ad5686_chip_info'
>   Warning: drivers/iio/dac/ad5686.h:95 Excess struct member 'channel'
>   description in 'ad5686_chip_info'
>
> Rename the entry to match the struct member.
>
> Fixes: 0357e488b825 ("iio:dac:ad5686: Refactor the driver")
> Assisted-by: LLM
> Signed-off-by: Arnav Kapoor <kapoorarnav43@gmail.com>
> ---
> Comment-only change, checked with scripts/kernel-doc -Wall.
>

Reviewed-by: Maxwell Doose <maxwell@maxwelld.cc>

Thanks,
Max

      reply	other threads:[~2026-10-11 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  4:51 [PATCH] iio: dac: ad5686: fix channels member name in kernel-doc Arnav Kapoor
2026-10-11 15:09 ` Maxwell Doose [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=DM23RGDMAP30.4KFLP01K5LSM@maxwelld.cc \
    --to=maxwell@maxwelld.cc \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=kapoorarnav43@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=rodrigo.alencar@analog.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.