[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiyxKDMW2fPumh2WyP3tP1BHpispjGfTWQ-we8keZ=q7Q@mail.gmail.com>
Date: Fri, 6 Sep 2019 17:58:43 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Will Deacon <will@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
"David S. Miller" <davem@...emloft.net>,
Paul Burton <paul.burton@...s.com>,
Sedat Dilek <sedat.dilek@...il.com>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Behan Webster <behanw@...il.com>,
Behan Webster <behanw@...verseincode.com>
Subject: Re: [GIT PULL] compiler-attributes for v5.3-rc8
On Fri, Sep 6, 2019 at 5:45 PM Nick Desaulniers <ndesaulniers@...gle.com> wrote:
>
> > Yes. With the appropriate test cycle
>
> Sedat reported the issue and already tested/verified the fix. How
> long should it sit in -next before sending a PR for inclusion to 5.3
> (as opposed to letting it ride out to 5.4)?
If the original patch was already in -next, I wouldn't worry about it,
as long as you do enough local testing that there's nothing stupid
going on.
The -next cycle is a few days, and even with an rc8 we're getting
close enough to release that I'd rather get it earlier than later. So
I'd rather get a pull request this weekend than then have to deal with
it when traveling next week.
Linus
Powered by blists - more mailing lists