From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [GIT PULL] gpio: fixes for v5.18-rc1
Date: Fri, 1 Apr 2022 16:00:16 +0200 [thread overview]
Message-ID: <20220401140016.831088-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following documentation and comment fixes for the
upcoming rc.
Best regards,
Bartosz Golaszewski
The following changes since commit f443e374ae131c168a065ea1748feac6b2e76613:
Linux 5.17 (2022-03-20 13:14:17 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.18-rc1
for you to fetch changes up to 24f71ae5447e661813228677d343208d624fc141:
gpio: ts5500: Fix Links to Technologic Systems web resources (2022-03-31 16:44:57 +0200)
----------------------------------------------------------------
gpio fixes for v5.18-rc1
- grammar and formatting fixes in comments for gpio-ts4900
- correct links in gpio-ts5500
- fix a warning in doc generation for the core GPIO documentation
----------------------------------------------------------------
Joey Gouly (1):
gpio: Properly document parent data union
Kris Bahnsen (2):
gpio: ts4900: Fix comment formatting and grammar
gpio: ts5500: Fix Links to Technologic Systems web resources
drivers/gpio/gpio-ts4900.c | 12 +++++++-----
drivers/gpio/gpio-ts5500.c | 4 ++--
include/linux/gpio/driver.h | 13 ++++++++-----
3 files changed, 17 insertions(+), 12 deletions(-)
next reply other threads:[~2022-04-01 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 14:00 Bartosz Golaszewski [this message]
2022-04-01 17:40 ` [GIT PULL] gpio: fixes for v5.18-rc1 pr-tracker-bot
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=20220401140016.831088-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).