From: Sedat Dilek <sedat.dilek@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Will Deacon <will@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Paul Burton <paul.burton@mips.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Behan Webster <behanw@gmail.com>,
Behan Webster <behanw@converseincode.com>
Subject: Re: [GIT PULL] compiler-attributes for v5.3-rc8
Date: Sat, 7 Sep 2019 07:52:21 +0000 [thread overview]
Message-ID: <CA+icZUVNATrXZ7SDTrKa10cK8xtrRiC6VeXjkP6e9WyeKstMnA@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wiyxKDMW2fPumh2WyP3tP1BHpispjGfTWQ-we8keZ=q7Q@mail.gmail.com>
On Sat, Sep 7, 2019 at 12:59 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Fri, Sep 6, 2019 at 5:45 PM Nick Desaulniers <ndesaulniers@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 -
next prev parent reply other threads:[~2019-09-07 5:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 18:18 [GIT PULL] compiler-attributes for v5.3-rc8 Miguel Ojeda
2019-09-05 6:23 ` Miguel Ojeda
2019-09-05 16:20 ` Linus Torvalds
2019-09-05 17:18 ` Nick Desaulniers
2019-09-05 17:22 ` Linus Torvalds
2019-09-05 19:53 ` Miguel Ojeda
2019-09-05 19:40 ` Miguel Ojeda
2019-09-05 20:53 ` Linus Torvalds
2019-09-06 20:11 ` Miguel Ojeda
2019-09-06 22:47 ` Nick Desaulniers
2019-09-06 23:11 ` Linus Torvalds
2019-09-07 0:06 ` Nick Desaulniers
2019-09-07 0:08 ` Linus Torvalds
2019-09-07 0:45 ` Nick Desaulniers
2019-09-07 0:58 ` Linus Torvalds
2019-09-07 7:52 ` Sedat Dilek [this message]
2019-09-07 11:59 ` Miguel Ojeda
2019-09-10 8:58 ` Sedat Dilek
2019-09-10 9:16 ` Miguel Ojeda
2019-09-08 13:19 Miguel Ojeda
2019-09-08 13:24 ` Miguel Ojeda
2019-09-08 17:25 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+icZUVNATrXZ7SDTrKa10cK8xtrRiC6VeXjkP6e9WyeKstMnA@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=behanw@converseincode.com \
--cc=behanw@gmail.com \
--cc=davem@davemloft.net \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=ndesaulniers@google.com \
--cc=paul.burton@mips.com \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).