linux-kernel - Re: [GIT PULL] Thermal-SoC management fixes for v5.0-rc6

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: <CAMwyc-QpYpwqFsGpKSZL1mHdggFYR-XeT9Nb0WgH5LNrgB1KMQ@mail.gmail.com>
Date:   Mon, 11 Feb 2019 15:05:13 -0500
From:   Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Eduardo Valentin <edubezval@...il.com>, pr-tracker-bot@...nel.org,
        Rui Zhang <rui.zhang@...el.com>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Thermal-SoC management fixes for v5.0-rc6

On Mon, 11 Feb 2019 at 13:40, Konstantin Ryabitsev
<konstantin@...uxfoundation.org> wrote:
> >> On Sun, Feb 10, 2019 at 04:25:16AM +0000, pr-tracker-bot@...nel.org wrote:
> >> > The pull request you sent on Sat, 9 Feb 2019 20:17:23 -0800:
> >> >
> >> > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes
> >> >
> >> > has been merged into torvalds/linux.git:
> >> > https://git.kernel.org/torvalds/c/7ad915f5ebf5b9e7ca98a7048d8f84a631fe388b
> >>
> >> I think the bot is off here because the above commit is about a merge
> >> from the linux-omap tree from Tony.
> >
> >Indeed.
> >
> >.. and the pr-tracker-bot thing actually made me ignore the pull
> >request, thinking I had left it in my inbox despite having pulled it.
> >
> >So it would be really good to know why pr-tracker-bot ended up
> >replying to the wrong email, because it can cause real problems.
>
> Simply put, it's because "it's a pull request sent to Linus." We
> currently don't disambiguate between Linus showing up in "To" or in "Cc"
> -- is that an important differentiation that should be enforced?

Linus:

Sorry, I totally misunderstood what you were saying -- I blame the jet
lag. I'll check out what's going on.

-K