Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20180803170550.164688-1-ndesaulniers@google.com>
 <tip-208cbb32558907f68b3b2a081ca2337ac3744794@git.kernel.org>
 <CAKwvOdmxaE7p-fgaaeCE17bbTf0iYmHQgWT2D6FM7U5fwUoN1Q@mail.gmail.com> <alpine.DEB.2.21.1808070924170.1788@nanos.tec.linutronix.de>
In-Reply-To: <alpine.DEB.2.21.1808070924170.1788@nanos.tec.linutronix.de>
From:   Nick Desaulniers <ndesaulniers@google.com>
Date:   Tue, 7 Aug 2018 09:46:46 -0700
Message-ID: <CAKwvOdnXqw_ZXD2tnPYdVdRtdKqi4hK5mLZ7ELyXMhrbNzyWfw@mail.gmail.com>
Subject: Re: [tip:x86/urgent] x86/irqflags: Provide a declaration for native_save_fl
To:     Thomas Gleixner <tglx@linutronix.de>
Cc:     hpa@zytor.com, david.laight@aculab.com,
        LKML <linux-kernel@vger.kernel.org>, jdelvare@suse.de,
        Ingo Molnar <mingo@kernel.org>,
        linux-tip-commits@vger.kernel.org, sedat.dilek@gmail.com
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner <tglx@linutronix.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@zytor.com> wrote:
> > > Cc: stable@vger.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@acuab.com>
> > Tested-by: Sedat Dilek <sedat.dilek@gmail.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