linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Richard Biener <rguenther@suse.de>, Nadav Amit <namit@vmware.com>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Michal Marek <michal.lkml@markovi.net>,
	linux-sparse@vger.kernel.org, Alok Kataria <akataria@vmware.com>,
	Juergen Gross <jgross@suse.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2] x86, kbuild: revert macrofying inline assembly code
Date: Fri, 21 Dec 2018 10:44:28 -0800	[thread overview]
Message-ID: <87woo23ek3.fsf@linux.intel.com> (raw)
In-Reply-To: <1544928632-9717-1-git-send-email-yamada.masahiro@socionext.com> (Masahiro Yamada's message of "Sun, 16 Dec 2018 11:50:32 +0900")

Masahiro Yamada <yamada.masahiro@socionext.com> writes:

> Revert the following 9 commits:

FWIW the -Wa additional also broke LTO builds because it doesn't really
support -Wa for individual files.

So I'm glad they got reverted.

-Andi

      parent reply	other threads:[~2018-12-21 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  2:50 [PATCH v2] x86, kbuild: revert macrofying inline assembly code Masahiro Yamada
2018-12-16  3:28 ` Nadav Amit
2018-12-17  2:54   ` Masahiro Yamada
2018-12-21 18:44 ` Andi Kleen [this message]

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=87woo23ek3.fsf@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=akataria@vmware.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=michal.lkml@markovi.net \
    --cc=mingo@redhat.com \
    --cc=namit@vmware.com \
    --cc=rguenther@suse.de \
    --cc=segher@kernel.crashing.org \
    --cc=tglx@linutronix.de \
    --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 NNTP newsgroup(s).