Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux GPIO <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-gpio for 6.18-1
Date: Thu, 23 Oct 2025 09:57:01 +0200	[thread overview]
Message-ID: <aPnfzZk30goFltb2@black.igk.intel.com> (raw)

Hi Linux GPIO  maintainers,

Emergency fixes for the regression found in last cycle. Please, pull for
v6.18-rc3.

Thanks,

With Best Regards,
Andy Shevchenko

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v6.18-1

for you to fetch changes up to b1055678a0160b2952c322ad1b61805562698f99:

  gpiolib: acpi: Use %pe when passing an error pointer to dev_err() (2025-10-23 08:40:46 +0200)

----------------------------------------------------------------
intel-gpio for v6.18-1

* Make set debounce errors non-fatal in GPIO ACPI case
* Use human readable error when printing a message in GPIO ACPI code

----------------------------------------------------------------
Andy Shevchenko (1):
      gpiolib: acpi: Use %pe when passing an error pointer to dev_err()

Hans de Goede (1):
      gpiolib: acpi: Make set debounce errors non fatal

 drivers/gpio/gpiolib-acpi-core.c | 31 +++++++++++++++++--------------
 1 file changed, 17 insertions(+), 14 deletions(-)

-- 
With Best Regards,
Andy Shevchenko



             reply	other threads:[~2025-10-23  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  7:57 Andy Shevchenko [this message]
2025-10-23  8:07 ` [GIT PULL] intel-gpio for 6.18-1 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=aPnfzZk30goFltb2@black.igk.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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