From: Will McVicker <willmcvicker@google.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Thierry Reding <treding@nvidia.com>
Cc: Edmond Chung <edmondchung@google.com>,
Andrew Chant <achant@google.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@android.com, Will McVicker <willmcvicker@google.com>
Subject: [PATCH v1 0/1] gpiolib: Don't free if pin ranges are not defined
Date: Mon, 30 Nov 2020 22:47:52 +0000 [thread overview]
Message-ID: <20201130224753.1569357-1-willmcvicker@google.com> (raw)
This patch fixes commit 2ab73c6d8323 ("gpio: Support GPIO controllers
without pin-ranges") where an imbalance of requests and frees to the
pinctrl driver were introduced.
Edmond Chung (1):
gpiolib: Don't free if pin ranges are not defined
drivers/gpio/gpiolib.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.29.2.454.gaff20da3a2-goog
next reply other threads:[~2020-11-30 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 22:47 Will McVicker [this message]
2020-11-30 22:47 ` [PATCH v1 1/1] gpiolib: Don't free if pin ranges are not defined Will McVicker
2020-12-01 14:41 ` 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=20201130224753.1569357-1-willmcvicker@google.com \
--to=willmcvicker@google.com \
--cc=achant@google.com \
--cc=bgolaszewski@baylibre.com \
--cc=edmondchung@google.com \
--cc=kernel-team@android.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.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 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.