On Sun, Feb 12, 2023 at 10:06 PM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> a13bbd841bf8 ("pinctrl: intel: Restore the pins that used to be in Direct IRQ mode")
>
> This is commit
>
> a8520be3ffef ("pinctrl: intel: Restore the pins that used to be in Direct IRQ mode")
>
> in Linus' tree.
This is really weird because my only copy of that patch was on the fixes branch
and that is what I sent to Torvalds.
When I check my tag pinctrl-v6.2-3 it's like this:
commit a8520be3ffef3d25b53bf171a7ebe17ee0154175 (HEAD, tag: pinctrl-v6.2-3)
Author: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Date: Mon Feb 6 16:15:59 2023 +0200
pinctrl: intel: Restore the pins that used to be in Direct IRQ mode
So that is what went to Torvalds' tree. It's also the only thing I
ever published to
the for-next branch, as it turns out after some git reflog in my working tree:
a8520be3ffef (HEAD, tag: pinctrl-v6.2-3) HEAD@{31}: reset: moving to fixes
a8520be3ffef (HEAD, tag: pinctrl-v6.2-3) HEAD@{39}: reset: moving to fixes
a8520be3ffef (HEAD, tag: pinctrl-v6.2-3) HEAD@{52}: reset: moving to fixes
a8520be3ffef (HEAD, tag: pinctrl-v6.2-3) HEAD@{55}: am: pinctrl:
intel: Restore the pins that used to be in Direct IRQ mode
So what is this a13bbd841bf8 patch coming from?
Yours,
Linus Walleij
