From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: stable@vger.kernel.org
Subject: Re: request (x86 + stack protector + paravirt + clang)
Date: Wed, 18 Jul 2018 11:07:02 +0200 [thread overview]
Message-ID: <20180718090702.GA6212@kroah.com> (raw)
In-Reply-To: <20180718084837.GA2375@kroah.com>
On Wed, Jul 18, 2018 at 10:48:37AM +0200, Greg KH wrote:
> On Tue, Jul 17, 2018 at 04:48:01PM -0700, Nick Desaulniers wrote:
> > Please cherry-pick upstream commits:
> >
> > d03db2b "compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline
> > declarations"
>
> This took a bunch of work to get it to work for 4.9, I didn't mess with
> it for 4.4.y, can you provide a patch series for that tree? Hm, I
> wonder if the same commits I did for 4.9.y would work there, let me try
> that first...
>
> > 0e2e160 "x86/asm: Add _ASM_ARG* constants for argument registers to <asm/asm.h>"
>
> This didn't work for 4.4.y either :(
>
> > d0a8d93 "x86/paravirt: Make native_save_fl() extern inline"
>
> This worked for all.
Oops, nope, it broke the build on 4.4.y, can you provide a working
backport for there?
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-18 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 23:48 request (x86 + stack protector + paravirt + clang) Nick Desaulniers
2018-07-18 8:48 ` Greg KH
2018-07-18 8:53 ` Greg KH
2018-07-18 9:07 ` Greg KH [this message]
2018-07-20 22:36 ` [4.4 STABLE BACKPORT] x86: paravirt: make native_save_fl extern inline Nick Desaulniers
2018-07-21 0:04 ` kbuild test robot
2018-07-21 0:06 ` Nick Desaulniers
2018-07-21 5:07 ` Greg KH
2018-07-21 5:08 ` Greg KH
2018-07-23 7:57 ` Greg KH
2018-07-20 22:45 ` request (x86 + stack protector + paravirt + clang) Nick Desaulniers
2018-07-21 5:07 ` Greg KH
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=20180718090702.GA6212@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ndesaulniers@google.com \
--cc=stable@vger.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).