linux-kernel - Re: [GIT PULL] pin control fixes for the v6.1 series

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: <CAHk-=win6D4mgA04-D+S96n4aTNU-hx94e2ftF7rQjHb46O0Kw@mail.gmail.com>
Date:   Fri, 21 Oct 2022 10:34:46 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] pin control fixes for the v6.1 series

On Fri, Oct 21, 2022 at 1:56 AM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> for you to fetch changes up to 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

Well, I have *no* idea what you did here, but the pull request claims
that I should fetch that Linux 6.1-rc1 commit, which I obviously
already have in my tree.

That's also why the pull request then doesn't have any diffstat
(because there's no diff), and why pr-tracket-bot immediately replied
with "it's already been merged".

And indeed, when I fetch that 'pinctrl-v6.1-2' tag, it does have your
signed tag, but it just points to my -rc1 commit.

In other words - can you please try that pull request again after
re-tagging properly - because it's all kinds of messed up right now.

                Linus