From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22`
Date: Fri, 14 Mar 2025 13:25:52 +0100 [thread overview]
Message-ID: <cb12d8d3-229c-4ef9-b585-778772b34ac7@molgen.mpg.de> (raw)
In-Reply-To: <CAMRc=Mez_3F0NifXLb18_XNH+-Q7D47HVOrYNt37EWsO9z0zgg@mail.gmail.com>
Dear Bartosz,
Am 14.03.25 um 13:19 schrieb Bartosz Golaszewski:
> On Fri, Mar 14, 2025 at 12:54 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>>>>>
>>>>> Brief looking at the error descriptions and the practical use the best (and
>>>>> unique enough) choice may be EBADSLT.
>>>>
>>>> In any case, I proposed to revert to the previous behavior in
>>>> gpiochip_add_data() in my follow-up series so the issue should soon go
>>>> away.
>>>
>>> Yes, I noted. The above is a material to discuss. We can make that semantics
>>> documented and strict and then one may filter out those errors if/when
>>> required.
>>
>> I am still seeing this with 6.14.0-rc6-00022-gb7f94fcf5546. Do you know,
>> if the reverts are going to be in the final 6.14 release?
>
> linux-next should probably be a better point of reference. I'm about
> to send out my PR to Linus so it'll be in 6.14-rc7 alright.
Awesome. Thank you!
Kind regards,
Paul
prev parent reply other threads:[~2025-03-14 12:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:40 Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22` Paul Menzel
2025-02-21 20:53 ` Bartosz Golaszewski
2025-02-21 21:02 ` Paul Menzel
2025-02-23 20:54 ` Bartosz Golaszewski
2025-02-23 22:04 ` Paul Menzel
2025-02-24 8:51 ` brgl
2025-02-25 20:43 ` Paul Menzel
2025-02-25 21:25 ` Linus Walleij
2025-02-26 13:37 ` Andy Shevchenko
2025-02-26 13:46 ` Andy Shevchenko
2025-02-26 14:14 ` Bartosz Golaszewski
2025-02-26 14:22 ` Andy Shevchenko
2025-03-14 11:54 ` Paul Menzel
2025-03-14 12:19 ` Bartosz Golaszewski
2025-03-14 12:25 ` Paul Menzel [this message]
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=cb12d8d3-229c-4ef9-b585-778772b34ac7@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).