From: William Breathitt Gray <wbg@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: William Breathitt Gray <wbg@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
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 1/3] gpio: 104-idio-16: Define maximum valid register address offset
Date: Sun, 19 Oct 2025 08:44:09 +0900 [thread overview]
Message-ID: <20251018234411.34877-1-wbg@kernel.org> (raw)
In-Reply-To: <aPPj22GL56sP1gOK@ashevche-desk.local>
On Sat, Oct 18, 2025 at 10:00:43PM +0300, Andy Shevchenko wrote:
> On Fri, Oct 17, 2025 at 09:58:01AM +0900, William Breathitt Gray wrote:
> > Attempting to load the 104-idio-16 module fails during regmap
> > initialization with a return error -EINVAL. This is a result of the
> > regmap cache failing initialization. Set the idio_16_regmap_config
> > max_register member to fix this failure.
>
> > Fixes: 2c210c9a34a3 ("gpio: 104-idio-16: Migrate to the regmap API")
> > Reported-by: Mark Cave-Ayland <mark.caveayland@nutanix.com>
> > Link: https://lore.kernel.org/r/9b0375fd-235f-4ee1-a7fa-daca296ef6bf@nutanix.com
>
> Link --> Closes ?
So that link points to a report detailing multiple bugs, but this patch
only fixes one of those bugs. Is it still appropriate to use Closes in
this case?
William Breathitt Gray
next prev parent reply other threads:[~2025-10-18 23:44 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 [this message]
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
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=20251018234411.34877-1-wbg@kernel.org \
--to=wbg@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).