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  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:   Wed, 16 Dec 2020 17:37:51 +0100
From:   Paolo Bonzini <>
To:     Sean Christopherson <>,
        Lai Jiangshan <>
        Lai Jiangshan <>,
Subject: Re: [PATCH V2] kvm: check tlbs_dirty directly

On 15/12/20 19:44, Sean Christopherson wrote:
> Note, you don't actually need to  when sending the
> patch.  If/when the patch is merged to Linus' tree, the stable tree maintainers,
> or more accurately their scripts, will automatically pick up the patch and apply
> it to the relevant stable trees.
> You'll probably be getting the following letter from Greg KH any time now:-)
> <formletter>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read:
> for how to do this properly.
> </formletter>

As far as I know, as long as he sees LKML or something else in Cc he 
assumes it's an indication _for the maintainer_.  Don't underestimate 
the power of Greg's mailing list filters. :)


Powered by blists - more mailing lists