From: Greg Kroah-Hartman <firstname.lastname@example.org> To: Dominique Martinet <email@example.com> Cc: Miguel Ojeda <firstname.lastname@example.org>, linux-kernel <email@example.com>, Rasmus Villemoes <firstname.lastname@example.org>, Eli Friedman <email@example.com>, Christopher Li <firstname.lastname@example.org>, Kees Cook <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Geert Uytterhoeven <email@example.com>, Masahiro Yamada <firstname.lastname@example.org>, Joe Perches <email@example.com>, Linus Torvalds <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH v2 2/2] Compiler Attributes: naked can be shared Date: Thu, 20 Sep 2018 09:22:05 +0200 [thread overview] Message-ID: <20180920072205.GC11963@kroah.com> (raw) In-Reply-To: <20180920001024.GD20280@nautica> On Thu, Sep 20, 2018 at 02:10:24AM +0200, Dominique Martinet wrote: > Miguel Ojeda wrote on Thu, Sep 20, 2018: > > > I've not followed so closely, in particular I'm not sure if it's the > > > only problem with arm32 right now, but that is a regression - the > > > general serie is meant as an improvement, but these two patches fix > > > 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h mutually > > > exclusive") which was taken in 4.19-rc1 > > > > > > (Miguel, perhaps a Fixes: tag might help remember that?) > > > > The commit is mentioned in the commit message, although not with the > > Fixes: syntax -- is something now automatically parsing that? I guess > > it is also easier for humans to parse :) > > As far as I'm aware, the backport to stable stuff parse these to know up > till how far back they should backport, but it still requires explicit > Cc to the stable@vger list... (not needed here as the "bad" commit never > made it to stable) > I'm not aware of anything else, but as you said, while I now see you > naming the commit now, I managed to miss it earlier and I was somewhat > following this so it's probably also easier on humans :) "Fixes:" is not just for stable, we use it wherever we have a patch that we know fixes a problem introduced in another patch. For this instance, I think we should just revert the offending patch, which should resolve the issue for everyone and then you can try to redo your series to get it right the next time. Sound good? > > > (If no-one in Cc has anything included in -next I could take them in my > > > 9p branch, but that is quite a bit out of scope from what I advertised > > > this branch as so I think it would be confusing ; I think it might > > > almost be best if Miguel will keep maintaining these in the future to do > > > his own request to inclusion in -next?) > > > > I can ask for my auxdisplay tree (or better, a new one) to be in -next > > and use that (are non-kernel.org trees allowed to be in -next, by the > > way?). > > I think a new one would be great, yes. > (my branch is on github, so Stephen does not appear to mind > non-kernel.org trees) Why not just route these through Andrew? He takes lots of stuff like this for this very reason. thanks, greg k-h
next prev parent reply other threads:[~2018-09-20 7:22 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 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 [this message] 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=20180920072205.GC11963@kroah.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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).