From: Linus Walleij <linusw@kernel.org>
To: Michael Walle <mwalle@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linusw@kernel.org>,
Alex Elder <elder@riscstar.com>,
Sashiko <sashiko-bot@kernel.org>
Subject: [PATCH v2 0/2] Improvement spotted during patch review.
Date: Fri, 08 May 2026 14:51:25 +0200 [thread overview]
Message-ID: <20260508-regmap-gpio-sparse-fixed-dir-v2-0-deee84df3027@kernel.org> (raw)
Support sparse unidirectional GPIO lines.
To be used in a forthcoming submission.
Signed-off-by: Linus Walleij <linusw@kernel.org>
---
Changes in v2:
- Make a second patch to exclude setting on unidirectional
lines.
- Link to v1: https://patch.msgid.link/20260507-regmap-gpio-sparse-fixed-dir-v1-1-a2e5855e2701@kernel.org
---
Linus Walleij (2):
gpio: regmap: Support sparsed fixed direction
gpio: regmap: Don't set a fixed direction line
drivers/gpio/gpio-regmap.c | 40 ++++++++++++++++++++++++++++++++++++----
include/linux/gpio/regmap.h | 7 +++++++
2 files changed, 43 insertions(+), 4 deletions(-)
---
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
change-id: 20260507-regmap-gpio-sparse-fixed-dir-1d5c0d2e2c6f
Best regards,
--
Linus Walleij <linusw@kernel.org>
next reply other threads:[~2026-05-08 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 12:51 Linus Walleij [this message]
2026-05-08 12:51 ` [PATCH v2 1/2] gpio: regmap: Support sparsed fixed direction Linus Walleij
2026-05-08 13:03 ` Alex Elder
2026-05-10 13:31 ` Alex Elder
2026-05-11 7:18 ` Michael Walle
2026-05-11 19:00 ` Linus Walleij
2026-05-08 12:51 ` [PATCH v2 2/2] gpio: regmap: Don't set a fixed direction line Linus Walleij
2026-05-11 7:24 ` Michael Walle
2026-05-11 9:56 ` [PATCH v2 0/2] Improvement spotted during patch review Bartosz Golaszewski
2026-05-11 12:15 ` Linus Walleij
2026-05-11 12:18 ` Alex Elder
2026-05-11 12:32 ` Bartosz Golaszewski
2026-05-11 12:39 ` Michael Walle
2026-05-11 12:44 ` 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=20260508-regmap-gpio-sparse-fixed-dir-v2-0-deee84df3027@kernel.org \
--to=linusw@kernel.org \
--cc=brgl@kernel.org \
--cc=elder@riscstar.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=sashiko-bot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.