linux-kernel - Re: linux-next: duplicate patch in the pinctrl-intel-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y+oZ7O9d8r8SIM0A@smile.fi.intel.com>
Date:   Mon, 13 Feb 2023 13:07:24 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the pinctrl-intel-fixes tree

On Mon, Feb 13, 2023 at 08:06:20AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> 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.

I believe this due to it's in my tree and not tagged. That's why it appeared in
the upper trees with different SHA. I'll drop mine.

-- 
With Best Regards,
Andy Shevchenko