From: "Michael Walle" <mwalle@kernel.org>
To: "Ioana Ciornei" <ioana.ciornei@nxp.com>
Cc: "William Breathitt Gray" <wbg@kernel.org>,
"Mark Cave-Ayland" <mark.caveayland@nutanix.com>,
<linus.walleij@linaro.org>, <brgl@bgdev.pl>,
<andriy.shevchenko@linux.intel.com>, <broonie@kernel.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: gpio: gpio-pci-idio-16 regression after LTS upgrade
Date: Tue, 14 Oct 2025 13:25:24 +0200 [thread overview]
Message-ID: <DDI0AO1RKDJK.1M31TW8HEJHFU@kernel.org> (raw)
In-Reply-To: <jajbilboyqty3a5tbgjgwklrpcstv7gotkqis46cuzgew7ip4q@ej37jq2cev77>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Tue Oct 14, 2025 at 1:21 PM CEST, Ioana Ciornei wrote:
>> To fix the regression, I guess the patch can then be picked up by the
>> stable team along with the driver patch which will set the
>> .fixed_direction_output config field.
>
> Just to make sure that I understand, do you want me to add another patch
> that adds the new driver user or that will be handled separately?
No, no. No new patch. It's just that your patch (just the one which
has that property added to gpio-regmap) has to be submitted to the stable
kernels (by the one who is fixing the regression) I guess.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-10-14 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 8:37 Mark Cave-Ayland
2025-10-07 8:16 ` William Breathitt Gray
2025-10-09 9:05 ` Mark Cave-Ayland
2025-10-09 9:49 ` William Breathitt Gray
2025-10-14 9:03 ` Michael Walle
2025-10-14 11:21 ` Ioana Ciornei
2025-10-14 11:25 ` Michael Walle [this message]
2025-10-14 11:40 ` Ioana Ciornei
2025-10-12 14:22 ` William Breathitt Gray
2025-10-13 10:32 ` 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=DDI0AO1RKDJK.1M31TW8HEJHFU@kernel.org \
--to=mwalle@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--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=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
all inboxes | Powered by JetHome®