From: Randy Dunlap <rdunlap@infradead.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Jonathan Corbet <corbet@lwn.net>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Arnd Bergmann <arnd@kernel.org>, Hans de Goede <hansg@kernel.org>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: gpio: add documentation about using software nodes
Date: Sat, 16 Aug 2025 15:21:44 -0700 [thread overview]
Message-ID: <f93c26c6-c390-46d4-bdd1-4d2f0e03e63d@infradead.org> (raw)
In-Reply-To: <8bdf668d-c120-4ed5-a0f4-fe8c0876c8d2@infradead.org>
On 8/16/25 3:08 PM, Randy Dunlap wrote:
> Hi,
>
> I have a few more nits...
>
>
> On 8/15/25 10:30 AM, Dmitry Torokhov wrote:
>> Introduce documentation regarding use of software nodes to describe
>> GPIOs on legacy boards that have not been converted to device tree.
>>
>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>> ---
>>
>> v2: Addressed Randy's comments.
>>
>> Documentation/driver-api/gpio/board.rst | 65 ++++
>> Documentation/driver-api/gpio/index.rst | 1 +
>> .../driver-api/gpio/legacy-boards.rst | 298 ++++++++++++++++++
>> 3 files changed, 364 insertions(+)
>>
> Overall, this looks good. Thanks.
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
I also tested the docs build and it looks good.
Tested-by: Randy Dunlap <rdunlap@infradead.org>
--
~Randy
next prev parent reply other threads:[~2025-08-16 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 17:30 Dmitry Torokhov
2025-08-16 22:08 ` Randy Dunlap
2025-08-16 22:21 ` Randy Dunlap [this message]
2025-08-16 23:17 ` Randy Dunlap
2025-08-17 20:28 ` Dmitry Torokhov
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=f93c26c6-c390-46d4-bdd1-4d2f0e03e63d@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@kernel.org \
--cc=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=hansg@kernel.org \
--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®