On Fri, Sep 6, 2019 at 5:45 PM Nick Desaulniers <ndesaulni...@google.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
