From: Cosmin Tanislav <demonsingur@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Linus Walleij <linusw@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] gpio: shared: another set of small fixes
Date: Thu, 8 Jan 2026 15:47:52 +0200 [thread overview]
Message-ID: <44b41858-fffa-411c-b4c0-a0c4da8a497b@gmail.com> (raw)
In-Reply-To: <CAMRc=Me5nNXU0foqToYs4W8fvbTZ0DZSRXAQ7rfHdbcoB4+7cQ@mail.gmail.com>
On 1/8/26 2:18 PM, Bartosz Golaszewski wrote:
> On Thu, Jan 8, 2026 at 1:13 PM Cosmin Tanislav <demonsingur@gmail.com> wrote:
>>
>> On 1/6/26 11:34 AM, Bartosz Golaszewski wrote:
>>> Here are three more patches fixing issues reported with shared GPIO
>>> management.
>>>
>>
>> I'm still getting some intermittent failures on today's next (which
>> contains this series).
>>
>> This does not seem to happen on every boot, so it might be some race.
>>
>
> Should be fixed by:
> https://lore.kernel.org/all/20260108102314.18816-1-bartosz.golaszewski@oss.qualcomm.com/
>
> Please give it a try and I'll queue it shortly.
>
Thank you, I can't seem to hit the issue anymore.
> Bart
next prev parent reply other threads:[~2026-01-08 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 9:34 Bartosz Golaszewski
2026-01-06 9:34 ` [PATCH v2 1/3] gpio: shared: assign the correct firmware node for reset-gpio use-case Bartosz Golaszewski
2026-01-06 9:34 ` [PATCH v2 2/3] gpio: shared: fix a race condition Bartosz Golaszewski
2026-01-06 9:34 ` [PATCH v2 3/3] gpio: shared: don't allocate the lookup table until we really need it Bartosz Golaszewski
2026-01-06 13:22 ` [PATCH v2 0/3] gpio: shared: another set of small fixes Mark Brown
2026-01-07 8:31 ` Bartosz Golaszewski
2026-01-08 12:13 ` Cosmin Tanislav
2026-01-08 12:18 ` Bartosz Golaszewski
2026-01-08 13:47 ` Cosmin Tanislav [this message]
2026-01-08 12:22 ` Marek Szyprowski
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=44b41858-fffa-411c-b4c0-a0c4da8a497b@gmail.com \
--to=demonsingur@gmail.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
/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®