From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v1 0/2] gpiolib: in-kernel documentation updates
Date: Tue, 26 Mar 2024 20:11:19 +0200 [thread overview]
Message-ID: <20240326181247.1419138-1-andriy.shevchenko@linux.intel.com> (raw)
While looking for something I have noticed that in-kernel documentation
for gpiolib implementation may be updated to reflect the current state
of affairs. Hence these two patches.
Andy Shevchenko (2):
gpiolib: Do not mention legacy GPIOF_* in the code
gpiolib: Up to date the kernel documentation
drivers/gpio/gpiolib-acpi.c | 45 ++--
drivers/gpio/gpiolib-cdev.c | 15 +-
drivers/gpio/gpiolib-devres.c | 85 ++++++--
drivers/gpio/gpiolib-legacy.c | 3 +
drivers/gpio/gpiolib-of.c | 102 +++++----
drivers/gpio/gpiolib-swnode.c | 8 +-
drivers/gpio/gpiolib-sysfs.c | 41 ++--
drivers/gpio/gpiolib.c | 388 +++++++++++++++++++++-------------
drivers/gpio/gpiolib.h | 8 +-
9 files changed, 438 insertions(+), 257 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2024-03-26 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 18:11 Andy Shevchenko [this message]
2024-03-26 18:11 ` [PATCH v1 1/2] gpiolib: Do not mention legacy GPIOF_* in the code Andy Shevchenko
2024-04-03 11:14 ` Bartosz Golaszewski
2024-03-26 18:11 ` [PATCH v1 2/2] gpiolib: Up to date the kernel documentation Andy Shevchenko
2024-04-03 12:59 ` Bartosz Golaszewski
2024-04-03 13:20 ` Andy Shevchenko
2024-04-03 10:50 ` [PATCH v1 0/2] gpiolib: in-kernel documentation updates Andy Shevchenko
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=20240326181247.1419138-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=warthog618@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).