From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [GIT PULL] gpio: fixes for v5.19-rc2
Date: Sat, 11 Jun 2022 22:27:32 +0200 [thread overview]
Message-ID: <20220611202732.6602-1-brgl@bgdev.pl> (raw)
Linus,
Here's a set of fixes for the upcoming rc. Most address the new warning we
emit at build time when irq chips are not immutable with some additional
tweaks to gpio-crystalcove from Andy and a small tweak to gpio-dwapd.
Please pull!
Bartosz Golaszewski
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.19-rc2
for you to fetch changes up to 77006f6edc0e0f58617eb25e53731f78641e820d:
gpio: dwapb: Don't print error on -EPROBE_DEFER (2022-06-10 14:26:15 +0200)
----------------------------------------------------------------
gpio fixes for v5.19-rc2
- make irq_chip structs immutable in several Diolan and intel drivers to
get rid of the new warning we emit when fiddling with irq chips
- don't print error messages on probe deferral in gpio-dwapb
----------------------------------------------------------------
Andy Shevchenko (7):
gpio: crystalcove: make irq_chip immutable
gpio: crystalcove: Use specific type and API for IRQ number
gpio: crystalcove: Join function declarations and long lines
gpio: wcove: make irq_chip immutable
gpio: merrifield: make irq_chip immutable
gpio: sch: make irq_chip immutable
gpio: dln2: make irq_chip immutable
Bartosz Golaszewski (1):
Merge tag 'intel-gpio-v5.19-2' of gitolite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel into gpio/for-current
Serge Semin (1):
gpio: dwapb: Don't print error on -EPROBE_DEFER
drivers/gpio/gpio-crystalcove.c | 70 ++++++++++++++++++++++-------------------
drivers/gpio/gpio-dln2.c | 23 ++++++++------
drivers/gpio/gpio-dwapb.c | 7 ++---
drivers/gpio/gpio-merrifield.c | 22 ++++++++-----
drivers/gpio/gpio-sch.c | 35 +++++++++++++--------
drivers/gpio/gpio-wcove.c | 10 ++++--
6 files changed, 99 insertions(+), 68 deletions(-)
next reply other threads:[~2022-06-11 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 20:27 Bartosz Golaszewski [this message]
2022-06-12 0:33 ` [GIT PULL] gpio: fixes for v5.19-rc2 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=20220611202732.6602-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--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