Linux IIO development
 help / color / mirror / Atom feed
From: Joshua Crofts <joshua.crofts1@gmail.com>
To: wrmfwv@163.com
Cc: nuno.sa@analog.com, jic23@kernel.org, robh@kernel.org,
	Michael.Hennerich@analog.com, dlechner@baylibre.com,
	andy@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux@analog.com, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tenglong Guo <admin@micronull.cn>,
	Sashiko AI <sashiko-bot@kernel.org>
Subject: Re: [PATCH v3] dt-bindings: iio: adc: add documentation for adi,ad7816
Date: Sun, 18 Oct 2026 17:39:44 +0200	[thread overview]
Message-ID: <20261018173756.35a0eca9@systembl0wer> (raw)
In-Reply-To: <20261018110015.39497-1-wrmfwv@163.com>

On Sun, 18 Oct 2026 19:00:15 +0800
wrmfwv@163.com wrote:

> From: Tenglong Guo <admin@micronull.cn>
> 
> Add a YAML binding document for the AD7816 family of ADCs.
> This fixes the checkpatch.pl warning about un-documented
> DT compatible strings in the staging driver.
> 
> Reviewed-by: Sashiko AI <sashiko-bot@kernel.org>

No, an AI cannot be credited in any tag (except in Assisted-by
but it will be deprecated). The v2 review returned several
issues as well, so it's definitely not worth a Reviewed-by tag
either.

As for the binding, I've sent a patch removing the AD7816 from
the kernel [1].

[1] https://lore.kernel.org/all/20261006115119.1416-1-joshua.crofts1@gmail.com/

-- 
Kind regards,
Joshua Crofts

      reply	other threads:[~2026-10-18 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 11:00 [PATCH v3] dt-bindings: iio: adc: add documentation for adi,ad7816 wrmfwv
2026-10-18 15:39 ` Joshua Crofts [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=20261018173756.35a0eca9@systembl0wer \
    --to=joshua.crofts1@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=admin@micronull.cn \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=wrmfwv@163.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