From: Stefan Agner <stefan@agner.ch> To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Nick Desaulniers <ndesaulniers@google.com>, Arnd Bergmann <arnd@arndb.de>, linux-kernel <linux-kernel@vger.kernel.org>, Rasmus Villemoes <linux@rasmusvillemoes.dk>, Eli Friedman <efriedma@codeaurora.org>, Christopher Li <sparse@chrisli.org>, Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>, Geert Uytterhoeven <geert@linux-m68k.org>, Masahiro Yamada <yamada.masahiro@socionext.com>, Joe Perches <joe@perches.com>, Dominique Martinet <asmadeus@codewreck.org>, Linus Torvalds <torvalds@linux-foundation.org>, linux-sparse@vger.kernel.org Subject: Re: [PATCH v2 2/2] Compiler Attributes: naked can be shared Date: Wed, 19 Sep 2018 23:00:37 -0700 [thread overview] Message-ID: <6837090afde15cd5ee155dbfabb0d556@agner.ch> (raw) In-Reply-To: <CANiq72kS_w7p3Xe9cDCjCA9j1u-zQ1-C4ZX7N8G+AbP4u7SG8w@mail.gmail.com> On 19.09.2018 16:00, Miguel Ojeda wrote: > On Wed, Sep 19, 2018 at 11:14 PM, Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: >> On Tue, Sep 18, 2018 at 08:56:04PM +0200, Miguel Ojeda wrote: >>> Hi Greg, >>> >> >>> Since Linus/Andrew/you >>> didn't comment on whether you wanted or not this for 4.19, we are >>> assuming they would go in for 4.20. However, Stefan/Nick/... wanted >>> this for 4.19 instead, they asked me to extract these patches two >>> separately for 4.19. I let them comment further on the status of Clang >>> on arm32. >> >> If these do not fix a regression, I don't see how they would be ready >> for 4.19-final. Clang on arm32 worked with v4.18 when using multi_v7_defconfig -CONFIG_EFI. With 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h mutually exclusive") it broke on v4.19-rc1. IMHO this is a regression and we should consider this two patches as a fix for it. > > Ok, I will wait a bit to send v5 until this is sorted out. > > [CC'd Nick, Stefan, Arnd: I just noticed the Reviewed-by/... lines > were not picked as CC]. Oh yeah thanks, really did not notice the discussion around v2 until you CC'd me now. -- Stefan > >> >>> I am going to send a v5 of the entire series without these two >>> patches, based on -rc4 (or -next, which one do you prefer? I would say >>> these patches should be applied early in the -next branches, so that >>> everyone is ready for the change, given it "touches" every translation >>> unit). >> >> That's up to whomever takes these into their tree for linux-next >> inclusion. If you are about to break everything, then you might >> consider changing your patches so they do not do that :) >> > > Well, the series shouldn't break anything (famous last words :), even > if everyone includes those headers. So, in theory, they *could* be > applied anywhere, anytime; but given they are global changes... > > Cheers, > Miguel
next prev parent reply other threads:[~2018-09-20 6:00 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-18 16:55 [PATCH v2 0/2] Compiler Attributes: (naked only, for v4.19) Miguel Ojeda 2018-09-18 16:55 ` [PATCH v2 1/2] Compiler Attributes: naked was fixed in gcc 4.6 Miguel Ojeda 2018-09-18 16:55 ` [PATCH v2 2/2] Compiler Attributes: naked can be shared Miguel Ojeda 2018-09-18 17:34 ` Greg Kroah-Hartman 2018-09-18 18:56 ` Miguel Ojeda 2018-09-19 21:14 ` Greg Kroah-Hartman 2018-09-19 23:00 ` Miguel Ojeda 2018-09-20 6:00 ` Stefan Agner [this message] 2018-09-20 7:19 ` Greg Kroah-Hartman 2018-09-20 7:20 ` Greg Kroah-Hartman 2018-09-19 23:05 ` Dominique Martinet 2018-09-19 23:56 ` Miguel Ojeda 2018-09-20 0:10 ` Dominique Martinet 2018-09-20 7:22 ` Greg Kroah-Hartman 2018-09-20 7:36 ` Dominique Martinet 2018-09-20 7:49 ` Geert Uytterhoeven 2018-09-20 16:11 ` Miguel Ojeda 2018-09-20 12:18 ` Miguel Ojeda 2018-09-20 13:57 ` [PATCH v2 0/2] Compiler Attributes: (naked only, for v4.19) Greg Kroah-Hartman 2018-09-20 13:59 ` Greg Kroah-Hartman 2018-09-20 16:13 ` Miguel Ojeda
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=6837090afde15cd5ee155dbfabb0d556@agner.ch \ --to=stefan@agner.ch \ --cc=arnd@arndb.de \ --cc=asmadeus@codewreck.org \ --cc=efriedma@codeaurora.org \ --cc=geert@linux-m68k.org \ --cc=gregkh@linuxfoundation.org \ --cc=joe@perches.com \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-sparse@vger.kernel.org \ --cc=linux@rasmusvillemoes.dk \ --cc=miguel.ojeda.sandonis@gmail.com \ --cc=mingo@kernel.org \ --cc=ndesaulniers@google.com \ --cc=sparse@chrisli.org \ --cc=torvalds@linux-foundation.org \ --cc=yamada.masahiro@socionext.com \ --subject='Re: [PATCH v2 2/2] Compiler Attributes: naked can be shared' \ /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
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).