From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.8-rc8
Date: Sat, 2 Mar 2024 11:34:49 +0100 [thread overview]
Message-ID: <20240302103449.4313-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following fixes for the next RC from the GPIO tree.
Thanks,
Bartosz
The following changes since commit d206a76d7d2726f3b096037f2079ce0bd3ba329b:
Linux 6.8-rc6 (2024-02-25 15:46:06 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.8-rc7
for you to fetch changes up to ec5c54a9d3c4f9c15e647b049fea401ee5258696:
gpio: fix resource unwinding order in error path (2024-03-01 09:33:30 +0100)
----------------------------------------------------------------
gpio fixes for v6.8-rc7
- fix resource freeing ordering in error path when adding a GPIO chip
- only set pins to output after the reset is complete in gpio-74x164
----------------------------------------------------------------
Andy Shevchenko (1):
gpiolib: Fix the error path order in gpiochip_add_data_with_key()
Arturas Moskvinas (1):
gpio: 74x164: Enable output pins after registers are reset
Bartosz Golaszewski (1):
gpio: fix resource unwinding order in error path
drivers/gpio/gpio-74x164.c | 4 ++--
drivers/gpio/gpiolib.c | 12 ++++++------
2 files changed, 8 insertions(+), 8 deletions(-)
next reply other threads:[~2024-03-02 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 10:34 Bartosz Golaszewski [this message]
2024-03-02 18:22 ` [GIT PULL] gpio: fixes for v6.8-rc8 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=20240302103449.4313-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--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