linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: linux-kbuild@vger.kernel.org
Cc: Matthias Kaehlcke <mka@chromium.org>,
	David Howells <dhowells@redhat.com>,
	Michael Davidson <md@google.com>, Michal Marek <mmarek@suse.com>,
	Jan Beulich <JBeulich@novell.com>,
	Alexander van Heukelum <heukelum@fastmail.fm>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Jeroen Hofstee <jeroen@myspectrum.nl>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] kbuild: cleanup asm-offset generation, and make it work with clang
Date: Fri, 14 Apr 2017 14:50:01 +0900	[thread overview]
Message-ID: <1492149003-19136-1-git-send-email-yamada.masahiro@socionext.com> (raw)

1/2 is a trivial cleanup of sed script
2/2 imports clang work-around from U-Boot.


Jeroen Hofstee (1):
  kbuild: fix asm-offset generation to work with clang

Masahiro Yamada (1):
  kbuild: consolidate redundant sed script ASM offset generation

 include/linux/kbuild.h | 6 +++---
 scripts/Makefile.lib   | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-14  5:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  5:50 Masahiro Yamada [this message]
2017-04-14  5:50 ` [PATCH 1/2] kbuild: consolidate redundant sed script ASM offset generation Masahiro Yamada
2017-04-14 16:51   ` Matthias Kaehlcke
2017-04-14  5:50 ` [PATCH 2/2] kbuild: fix asm-offset generation to work with clang Masahiro Yamada
2017-04-14 17:44   ` Matthias Kaehlcke
2017-04-18  9:57 ` [PATCH 1/2] kbuild: consolidate redundant sed script ASM offset generation David Howells
2017-04-18 10:20   ` Masahiro Yamada
2017-04-18 13:15   ` David Howells
2017-04-18 14:03     ` Masahiro Yamada

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=1492149003-19136-1-git-send-email-yamada.masahiro@socionext.com \
    --to=yamada.masahiro@socionext.com \
    --cc=JBeulich@novell.com \
    --cc=dhowells@redhat.com \
    --cc=heukelum@fastmail.fm \
    --cc=jeroen@myspectrum.nl \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@google.com \
    --cc=mka@chromium.org \
    --cc=mmarek@suse.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).