From: Jonathan Cameron <jic23@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Ammar Mustafa" <ammarmustafa34@gmail.com>,
"Alisa-Dariana Roman" <alisa.roman@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Docs: iio: ad7191 Correct clock configuration
Date: Sun, 12 Apr 2026 14:40:20 +0100 [thread overview]
Message-ID: <20260412144020.502dafd9@jic23-huawei> (raw)
In-Reply-To: <CAMuHMdUcDrDR-1f5eXjdyDR3-HcTFFeGsmYU2whV=fQhzsCNtg@mail.gmail.com>
On Mon, 30 Mar 2026 10:09:28 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Sat, 28 Feb 2026 at 11:51, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > On Fri, Feb 27, 2026 at 02:08:33PM -0500, Ammar Mustafa wrote:
> > > Correct the ad7191 documentation to match the datasheet:
> > > - Fix inverted CLKSEL pin logic: device uses external clock when pin is
> > > inactive, and internal CMOS/crystal when high.
> >
> > high --> active
>
> Thanks for your patch, which is now commit d2a4ec19d2a2e54c ("Docs:
> iio: ad7191 Correct clock configuration") in char-misc-next and
> iio/togreg.
>
> That commit message still says "inactive" and "high", thus adding to
> the confustion.
>
> Gr{oetje,eeting}s,
>
> Geert
>
Ah. Sorry, I missed that and can't really do anything to fix it up
now :( All got a bit rushed as I was off on holiday.
Jonathan
prev parent reply other threads:[~2026-04-12 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 19:08 [PATCH v2] Docs: iio: ad7191 Correct clock configuration Ammar Mustafa
2026-02-28 10:50 ` Andy Shevchenko
2026-03-22 12:13 ` Jonathan Cameron
2026-03-26 22:04 ` Ammar Mustafa
2026-03-27 7:31 ` Jonathan Cameron
2026-03-30 8:09 ` Geert Uytterhoeven
2026-04-12 13:40 ` 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=20260412144020.502dafd9@jic23-huawei \
--to=jic23@kernel.org \
--cc=alisa.roman@analog.com \
--cc=ammarmustafa34@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=skhan@linuxfoundation.org \
/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