Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: William Breathitt Gray <wbg@kernel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Michael Walle <mwalle@kernel.org>,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Mark Brown <broonie@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Cave-Ayland <mark.caveayland@nutanix.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] gpio: idio-16: Fix regmap initialization errors
Date: Sat, 18 Oct 2025 22:03:21 +0300	[thread overview]
Message-ID: <aPPkeRLgxobzoNlb@ashevche-desk.local> (raw)
In-Reply-To: <20251017-fix-gpio-idio-16-regmap-v1-0-a7c71080f740@kernel.org>

On Fri, Oct 17, 2025 at 09:58:00AM +0900, William Breathitt Gray wrote:
> The migration of IDIO-16 GPIO drivers to the regmap API resulted in some
> regressions to the gpio-104-idio-16, gpio-pci-idio-16, and gpio-idio-16
> modules. Specifically, the 104-idio-16 and pci-idio-16 GPIO drivers
> utilize regmap caching and thus must set max_register for their
> regmap_config, while gpio-idio-16 requires fixed_direction_output to
> represent the fixed direction of the IDIO-16 GPIO lines. Fixes for these
> regressions are provided by this series.

With commit message amendment and Cc list (as per Bart's message),
feel free to add
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2025-10-18 19:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  0:58 [PATCH 0/3] gpio: idio-16: Fix regmap initialization errors William Breathitt Gray
2025-10-17  0:58 ` [PATCH 1/3] gpio: 104-idio-16: Define maximum valid register address offset William Breathitt Gray
2025-10-18 19:00   ` Andy Shevchenko
2025-10-18 19:01     ` Andy Shevchenko
2025-10-18 23:44     ` William Breathitt Gray
2025-10-20  8:01       ` Andy Shevchenko
2025-10-17  0:58 ` [PATCH 2/3] gpio: pci-idio-16: " William Breathitt Gray
2025-10-17  0:58 ` [PATCH 3/3] gpio: idio-16: Define fixed direction of the GPIO lines William Breathitt Gray
2025-10-17  8:26 ` [PATCH 0/3] gpio: idio-16: Fix regmap initialization errors Bartosz Golaszewski
2025-10-18 19:03 ` Andy Shevchenko [this message]
2025-10-20 13:47 ` Mark Cave-Ayland

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=aPPkeRLgxobzoNlb@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=broonie@kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.caveayland@nutanix.com \
    --cc=mwalle@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wbg@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