From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 0/3] gpiolib: fix a regression introduced by gpio_do_set_config()
Date: Mon, 3 Feb 2020 14:30:23 +0100 [thread overview]
Message-ID: <20200203133026.22930-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
These three patches fix a regression introduced by commit d90f36851d65
("gpiolib: have a single place of calling set_config()"). We first need
to revert patches that came on top of it, then apply the actual fix.
Bartosz Golaszewski (3):
Revert "gpiolib: Remove duplicated function gpio_do_set_config()"
Revert "gpiolib: remove set but not used variable 'config'"
gpiolib: fix gpio_do_set_config()
drivers/gpio/gpiolib.c | 31 ++++++++++++++++++++++++++-----
1 file changed, 26 insertions(+), 5 deletions(-)
--
2.23.0
next reply other threads:[~2020-02-03 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 13:30 Bartosz Golaszewski [this message]
2020-02-03 13:30 ` [PATCH 1/3] Revert "gpiolib: Remove duplicated function gpio_do_set_config()" Bartosz Golaszewski
2020-02-03 13:30 ` [PATCH 2/3] Revert "gpiolib: remove set but not used variable 'config'" Bartosz Golaszewski
2020-02-03 13:30 ` [PATCH 3/3] gpiolib: fix gpio_do_set_config() Bartosz Golaszewski
2020-02-03 14:31 ` [PATCH 0/3] gpiolib: fix a regression introduced by gpio_do_set_config() Andy Shevchenko
2020-02-03 14:35 ` Bartosz Golaszewski
2020-02-03 14:56 ` Andy Shevchenko
2020-02-03 19:14 ` Guenter Roeck
2020-02-04 9:46 ` 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=20200203133026.22930-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 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.