From: Guenter Roeck <linux@roeck-us.net>
To: Linus Walleij <linus.walleij@linaro.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [GIT PULL] pin control fixes for the v5.17 series
Date: Mon, 28 Feb 2022 06:59:40 -0800 [thread overview]
Message-ID: <84401f5e-38a3-04b1-eac5-5ab1d0ab5e09@roeck-us.net> (raw)
In-Reply-To: <CACRpkdbWkm1WDY30qoGLEQba+G2cDEhT+M8nCdJbcD=ZQiu6uw@mail.gmail.com>
On 2/28/22 06:43, Linus Walleij wrote:
> On Sun, Feb 27, 2022 at 9:38 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> On Sat, Feb 26, 2022 at 5:11 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>>>
>>> some more pin control fixes that trickled in the last week or
>>> two.
>>
>> Hmm. Am I confused because I thought I'd see a fix for the orangepi
>> problem that Guenter has been reporting?
>>
>> That problem has been pending for quite a while now.
>
> OK let's poke Hans, he usually fix things quickly so it must have been missed.
>
> Hans did you see Guenthers remark here:
> https://lore.kernel.org/linux-gpio/20220128172003.GA2666058@roeck-us.net/
>
> Do you want to attempt patching it or shall I just revert the patch for now?
>
> Yours,
> Linus Walleij
The fix has long since been submitted and is available in linux-next.
From my notes:
Fix posted at
https://patchwork.kernel.org/project/linux-media/patch/0f536cd8-01db-5d16-2cec-ec6d19409a49@xs4all.nl/
and in linux-next as commit 3c5412cdec9f ("pinctrl-sunxi:
sunxi_pinctrl_gpio_direction_in/output: use correct offset").
The fix exposes a lockdep splat for which a fix is posted at
https://lore.kernel.org/lkml/20220216040037.22730-1-samuel@sholland.org/
This patch is available in linux-next as commit 4649b97042c3 ("pinctrl:
sunxi: Use unique lockdep classes for IRQs").
Guenter
next prev parent reply other threads:[~2022-02-28 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 1:11 Linus Walleij
2022-02-27 20:38 ` Linus Torvalds
2022-02-28 14:43 ` Linus Walleij
2022-02-28 14:59 ` Guenter Roeck [this message]
2022-02-28 15:01 ` Hans Verkuil
2022-02-28 19:14 ` Linus Torvalds
2022-02-28 22:49 ` Linus Walleij
2022-03-01 1:02 ` Linus Torvalds
2022-02-27 21:22 ` pr-tracker-bot
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=84401f5e-38a3-04b1-eac5-5ab1d0ab5e09@roeck-us.net \
--to=linux@roeck-us.net \
--cc=hverkuil@xs4all.nl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®