On Sat, Sep 7, 2019 at 12:59 AM Linus Torvalds <torva...@linux-foundation.org> wrote: > > 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. >
I am the original reporter and tester of the ClangBuiltLinux issue #619 and highly appreciate to have the single fix in Linux v5.3 final. The compiler-attribute patchset sit for some weeks in linux-next, so I have not seen any complains. What I still prefer is to re-integrate the arm64 and sh arch related patches which went through maintainer's trees in linux-next. AFAICS some massage of the commit messages were missing, too. devil's OMG dileks used compiler and linker: LLVM/Clang and LLD v9.0.0-rc3 > 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. > +1 for ASAPISSIMO Thanks for taking care. - Sedat -
