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: <alpine.DEB.2.21.1808070924170.1788@nanos.tec.linutronix.de>
Date:   Tue, 7 Aug 2018 09:29:27 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
cc:     hpa@...or.com, david.laight@...lab.com,
        LKML <linux-kernel@...r.kernel.org>, jdelvare@...e.de,
        Ingo Molnar <mingo@...nel.org>,
        linux-tip-commits@...r.kernel.org, sedat.dilek@...il.com
Subject: Re: [tip:x86/urgent] x86/irqflags: Provide a declaration for
 native_save_fl

On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> On Sun, Aug 5, 2018 at 1:33 PM tip-bot for Nick Desaulniers
> <tipbot@...or.com> wrote:
> > Cc: stable@...r.kernel.org
> 
> Not sure if this was going to be cleaned up in an automated way, but
> looks like this commit message drops the comment to stable as to how
> far back it should go:
> 
> # 4.17, 4.14, 4.9, 4.4

The Fixes tag is enough. If the upstream commit was backported, then the
tools of the stable folks will find it and know exactly how far it needs to
go back.

> also, there were tested by's reported:
> 
> Tested-by: David Laight <david.laight@...ab.com>
> Tested-by: Sedat Dilek <sedat.dilek@...il.com>

Which came in after I applied it....

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ