From: Randy Dunlap <rdunlap@infradead.org>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Levente Révész" <levente.revesz@eilabs.com>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1 1/1] Documentation: gpio: Add a compatibility and feature list for PCA953x
Date: Wed, 12 Nov 2025 16:32:38 -0800 [thread overview]
Message-ID: <da641dee-0481-4392-aeb2-1573239d2fb3@infradead.org> (raw)
In-Reply-To: <20251112224924.2091880-1-andriy.shevchenko@linux.intel.com>
On 11/12/25 2:48 PM, Andy Shevchenko wrote:
> From: Levente Révész <levente.revesz@eilabs.com>
>
> I went through all the datasheets and created this note listing
> chip functions and register layouts.
>
> Signed-off-by: Levente Révész <levente.revesz@eilabs.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>
> inline reply --> v1: made a formal patch, converted to reST format
>
> Documentation/driver-api/gpio/index.rst | 1 +
> Documentation/driver-api/gpio/pca953x.rst | 552 ++++++++++++++++++++++
> 2 files changed, 553 insertions(+)
> create mode 100644 Documentation/driver-api/gpio/pca953x.rst
Wowsa. That's a lot of info.
Looks good. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
--
~Randy
next prev parent reply other threads:[~2025-11-13 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 22:48 Andy Shevchenko
2025-11-12 23:04 ` Linus Walleij
2025-11-13 0:32 ` Randy Dunlap [this message]
2025-11-15 1:25 ` Bagas Sanjaya
2025-11-18 18:55 ` Andy Shevchenko
2025-11-19 0:55 ` Bagas Sanjaya
2025-11-19 7:51 ` Bartosz Golaszewski
2025-11-19 9:11 ` Andy Shevchenko
2025-11-19 11:06 ` Bagas Sanjaya
2025-11-19 11:08 ` Bartosz Golaszewski
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=da641dee-0481-4392-aeb2-1573239d2fb3@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=levente.revesz@eilabs.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®