From: "Léo DUBOIN" <lduboin@freebox.fr>
To: linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Léo DUBOIN" <lduboin@freebox.fr>
Subject: [PATCH 0/2] pinctrl: core: fix untreated named gpio ranges in pinctrl_pins_show()
Date: Thu, 25 Apr 2024 15:58:00 +0200 [thread overview]
Message-ID: <cover.1714049455.git.lduboin@freebox.fr> (raw)
This series covers errors I encountered with the pinctrl_pins_show()
function when dealing with named gpio ranges generated through the
device tree using 'gpio-ranges-group-names'.
These errors were introduced with the original implementation in
f1b206cf7c57561ea156798f323b0541a783bd2f.
Léo DUBOIN (2):
pinctrl: core: take into account the pins array in pinctrl_pins_show()
pinctrl: core: reset gpio_device in loop in pinctrl_pins_show()
drivers/pinctrl/core.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--
2.42.0
WARNING: multiple messages have this Message-ID (diff)
From: "Léo DUBOIN" <lduboin@freebox.fr>
To: linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Léo DUBOIN" <lduboin@freebox.fr>
Subject: [PATCH RESEND 0/2] pinctrl: core: fix untreated named gpio ranges in pinctrl_pins_show()
Date: Fri, 10 May 2024 18:25:37 +0200 [thread overview]
Message-ID: <cover.1714049455.git.lduboin@freebox.fr> (raw)
Message-ID: <20240510162537.p8CzDpoT1jBA3WlqPDTuNCyrXXGgMfIc5ey7chvEmAU@z> (raw)
This series covers errors I encountered with the pinctrl_pins_show()
function when dealing with named gpio ranges generated through the
device tree using 'gpio-ranges-group-names'.
These errors were introduced with the original implementation in
f1b206cf7c57561ea156798f323b0541a783bd2f.
Léo DUBOIN (2):
pinctrl: core: take into account the pins array in pinctrl_pins_show()
pinctrl: core: reset gpio_device in loop in pinctrl_pins_show()
drivers/pinctrl/core.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--
2.42.0
next reply other threads:[~2024-04-25 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 13:58 Léo DUBOIN [this message]
2024-04-25 13:58 ` [PATCH 1/2] pinctrl: core: take into account the pins array in pinctrl_pins_show() Léo DUBOIN
2024-05-10 16:25 ` [PATCH RESEND " Léo DUBOIN
2024-04-25 13:58 ` [PATCH 2/2] pinctrl: core: reset gpio_device in loop " Léo DUBOIN
2024-05-10 16:25 ` [PATCH RESEND " Léo DUBOIN
2024-05-10 16:25 ` [PATCH RESEND 0/2] pinctrl: core: fix untreated named gpio ranges " Léo DUBOIN
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=cover.1714049455.git.lduboin@freebox.fr \
--to=lduboin@freebox.fr \
--cc=linus.walleij@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).