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] [day] [month] [year] [list]
Message-ID: <CACRpkdYrBpUZAcJMvXMouW08RW+6LYzPraeJdDFv+yQRzoqWrA@mail.gmail.com>
Date:   Mon, 13 Feb 2023 14:43:22 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        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 12:07 PM Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
> 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.

Ah, also the $subject says "intel pinctrl fixes" tree, not the
"pinctrl fixes" :P

My attention to detail is lacking today, like all days...

Yours,
Linus Walleij

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ