All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Kees Cook <keescook@chromium.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [GIT PULL] pin control bulk changes for v5.18
Date: Mon, 28 Mar 2022 14:41:33 -0700	[thread overview]
Message-ID: <CAHk-=wjxvNGEUUN5fj203KJL8qXK3jv359Ketc-HJMJU9wN6KA@mail.gmail.com> (raw)
In-Reply-To: <YkIqyb6lhn5uU2jb@latitude>

On Mon, Mar 28, 2022 at 2:38 PM Jonathan Neuschäfer
<j.neuschaefer@gmx.net> wrote:
>
> It was — but when it was noticed, the fix went through the IRQ tree, on
> top of a refactoring that happened there (the switch to generic_handle_domain_irq):
>
> https://lore.kernel.org/lkml/164751044707.389.16417510835118111853.tip-bot2@tip-bot2/

Ok, that ends up at least being identical to what I did, so thats' good.

> When I added the pinctrl-wpcm450 driver, I changed the pinctrl/nuvoton/
> directory to obj-y and exposed the pinctrl-npcm7xx to CI bot testing.
> The bug existed, untouched, since the driver was added a few years ago.

Ahh. Good. So not a heisenbug, just happened to be hidden before.

Thanks for clarifying,

                 Linus

  reply	other threads:[~2022-03-28 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 13:08 [GIT PULL] pin control bulk changes for v5.18 Linus Walleij
2022-03-28 19:11 ` Linus Torvalds
2022-03-28 21:38   ` Jonathan Neuschäfer
2022-03-28 21:41     ` Linus Torvalds [this message]
2022-03-29 16:15       ` Linus Walleij
2022-03-28 19:15 ` 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='CAHk-=wjxvNGEUUN5fj203KJL8qXK3jv359Ketc-HJMJU9wN6KA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=keescook@chromium.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.