From: Richard Biener <rguenther@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Nadav Amit <namit@vmware.com>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
matz@suse.de, gcc@gcc.gnu.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
Alok Kataria <akataria@vmware.com>,
Christopher Li <sparse@chrisli.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jan Beulich <JBeulich@suse.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Juergen Gross <jgross@suse.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
linux-sparse@vger.kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
virtualization@lists.linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
linux-xtensa@linux-xtensa.org
Subject: Re: PROPOSAL: Extend inline asm syntax with size spec
Date: Thu, 29 Nov 2018 13:52:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1811291423490.1827@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20181129131611.GC3070@nazgul.tnic>
On Thu, 29 Nov 2018, Borislav Petkov wrote:
> On Thu, Nov 29, 2018 at 02:09:25PM +0100, Richard Biener wrote:
> > I'd be not opposed to backporting the asm inline support.
>
> Even better! :-)
>
> > Of course we still have to be happy with it and install the patch ;)
> >
> > Are you (kernel folks) happy with asm inline ()?
>
> Yes, I think we are:
>
> https://lkml.kernel.org/r/20181031125526.GA13219@hirez.programming.kicks-ass.net
OK, Segher - can you ping the latest version of the patch please?
Thanks,
Richard.
next prev parent reply other threads:[~2018-11-29 13:25 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181003213100.189959-1-namit@vmware.com>
2018-10-07 9:46 ` Borislav Petkov
2018-10-07 13:23 ` Segher Boessenkool
2018-10-07 14:14 ` Borislav Petkov
2018-10-07 15:14 ` Segher Boessenkool
[not found] ` <20181008055838.GA66819@gmail.com>
2018-10-08 7:53 ` Segher Boessenkool
2018-10-07 15:53 ` Michael Matz
2018-10-08 7:31 ` Segher Boessenkool
2018-10-08 9:09 ` Richard Biener
2018-10-08 10:03 ` Segher Boessenkool
2018-10-09 15:54 ` Segher Boessenkool
2018-10-10 7:12 ` Richard Biener
2018-10-10 7:54 ` Segher Boessenkool
[not found] ` <20181010072240.GB103159@gmail.com>
2018-10-10 8:03 ` Segher Boessenkool
2018-10-10 8:19 ` Borislav Petkov
2018-10-10 8:36 ` Richard Biener
2018-10-10 18:55 ` Segher Boessenkool
2018-10-10 19:14 ` Borislav Petkov
2018-10-13 19:33 ` Borislav Petkov
[not found] ` <alpine.LNX.2.20.13.1810132355180.13914@monopod.intra.ispras.ru>
2018-10-13 21:31 ` Borislav Petkov
2018-10-25 10:23 ` Borislav Petkov
[not found] ` <20181031125526.GA13219@hirez.programming.kicks-ass.net>
2018-10-31 22:04 ` Segher Boessenkool
2018-11-01 5:23 ` Joe Perches
[not found] ` <20181101090114.GE3159@hirez.programming.kicks-ass.net>
2018-11-01 9:20 ` Joe Perches
2018-10-10 10:29 ` Richard Biener
2018-10-10 16:31 ` Nadav Amit
2018-10-10 19:31 ` Segher Boessenkool
2018-10-11 7:05 ` Richard Biener
[not found] ` <CAK7LNARmrdtyE7JRAdJH_zbfvD_cej+TGLh+5KfT20o538KUcA@mail.gmail.com>
2018-11-29 13:09 ` Borislav Petkov via gcc
2018-11-29 13:16 ` Richard Biener
2018-11-29 13:25 ` Borislav Petkov via gcc
2018-11-29 13:52 ` Richard Biener [this message]
2018-11-30 9:06 ` Segher Boessenkool
2018-11-30 10:04 ` Boris Petkov via gcc
2018-12-02 6:03 ` Segher Boessenkool
[not found] ` <20181008061323.GB66819@gmail.com>
2018-10-08 8:19 ` Segher Boessenkool
[not found] ` <4F2F1BCE-7875-4160-9E1E-9F8EF962D989@vmware.com>
2018-10-07 16:13 ` [RESEND] " Nadav Amit
2018-10-07 16:46 ` Richard Biener
2018-10-07 19:06 ` Nadav Amit
2018-10-07 19:52 ` Jeff Law
2018-10-08 7:46 ` Richard Biener
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=alpine.LSU.2.20.1811291423490.1827@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=JBeulich@suse.com \
--cc=akataria@vmware.com \
--cc=bp@alien8.de \
--cc=chris@zankel.net \
--cc=gcc@gcc.gnu.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jcmvbkbc@gmail.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=matz@suse.de \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=sam@ravnborg.org \
--cc=segher@kernel.crashing.org \
--cc=sparse@chrisli.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).