linux-kernel - Re: [GIT PULL] Hyper-V commits for 5.6-rc

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: <CAHk-=wisKNsaOOCO8TfigKwmuqX83+KvntYeGq-KbOcSPunQbg@mail.gmail.com>
Date:   Thu, 5 Mar 2020 12:28:48 -0600
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Wei Liu <wei.liu@...nel.org>
Cc:     kys@...rosoft.com, Stephen Hemminger <sthemmin@...rosoft.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-hyperv@...r.kernel.org, mikelley@...rosoft.com,
        Sasha Levin <sashal@...nel.org>, haiyangz@...rosoft.com
Subject: Re: [GIT PULL] Hyper-V commits for 5.6-rc

On Thu, Mar 5, 2020 at 9:59 AM Wei Liu <wei.liu@...nel.org> wrote:
>
> This is mostly a "dry-run" attempt to sort out any wrinkles on my end.
> If I have done something stupid, let me know.

Looks fine. I generally like seeing the commits being a bit older than
these are - you seem to have applied or rebased them not all that long
before sending the pull request. I prefer seeing that they've been in
linux-next etc, but for soemthing small like this I guess it doesn't
much matter. Next time?

Also, it would generally be lovely to see signatures of the old
maintainer on the new maintainer's pgp key when transitions like this
happen, but it's not like we've really required that in the past
either. Literally just a "that would be nice"

                Linus