From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [PATCH v2 2/2] Compiler Attributes: naked can be shared Date: Thu, 20 Sep 2018 09:20:25 +0200 Message-ID: <20180920072025.GB11963@kroah.com> References: <20180918165542.4691-1-miguel.ojeda.sandonis@gmail.com> <20180918165542.4691-3-miguel.ojeda.sandonis@gmail.com> <20180918173428.GA21591@kroah.com> <20180919211458.GA8757@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Miguel Ojeda Cc: Nick Desaulniers , Arnd Bergmann , Stefan Agner , linux-kernel , Rasmus Villemoes , Eli Friedman , Christopher Li , Kees Cook , Ingo Molnar , Geert Uytterhoeven , Masahiro Yamada , Joe Perches , Dominique Martinet , Linus Torvalds , linux-sparse@vger.kernel.org List-Id: linux-sparse@vger.kernel.org On Thu, Sep 20, 2018 at 01:00:41AM +0200, Miguel Ojeda wrote: > >> 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... It doesn't matter the "order" in which global changes are added to linux-next. If you think it does, please work with the linux-next maintainer to properly place your tree in the correct "location". thanks, greg k-h