linux-kernel - Re: Missing [GIT PULL] request for <tip.git#locking-urgent-2020-10-11>

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]

Date:   Mon, 12 Oct 2020 16:35:14 +0200
From:   Sedat Dilek <sedat.dilek@...il.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Missing [GIT PULL] request for <tip.git#locking-urgent-2020-10-11>

On Mon, Oct 12, 2020 at 3:42 PM Ingo Molnar <mingo@...nel.org> wrote:
>
>
> * Sedat Dilek <sedat.dilek@...il.com> wrote:
>
> > Hi,
> >
> > yesterday, I saw Ingo tagged "locking-urgent-2020-10-11" in tip Git.
> >
> > Did you drop it or was this for Linux v5.9 final and the git-pull
> > request was simply forgotten?
> >
> > Just curious.
>
> So I ran the pull request script to send the tree to Linus, but on final
> review decided not to send it, as there was a pending bugreport against the
> tree, it was very late in the cycle and the commits were pretty fresh. I
> sent two other trees (x86/urgent and perf/urgent).
>
> This is why there's a signed tag for locking/urgent, but no pull request.
> :-)
>

OK, I see and thanks for the information.

- Sedat -