linux-kernel - Re: [tip:x86/urgent] x86/irqflags: Provide a declaration for native_save

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: <CAKwvOdnXqw_ZXD2tnPYdVdRtdKqi4hK5mLZ7ELyXMhrbNzyWfw@mail.gmail.com>
Date:   Tue, 7 Aug 2018 09:46:46 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Thomas Gleixner <tglx@...utronix.de>
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 Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> 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.

Oh, cool.

> > 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....

I've seen other maintainers revise commit messages before sending pull
requests along, but I guess that's problematic as anyone else who has
pulled before the revision would then have a merge conflict.
-- 
Thanks,
~Nick Desaulniers