From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] kbuild: Refactor ./Kbuild
Date: Mon, 5 Jan 2015 15:57:14 +0900 [thread overview]
Message-ID: <1420441036-5289-1-git-send-email-yamada.m@jp.panasonic.com> (raw)
Changes in v2:
- Pass the include guard as an argument of cmd_offsets
as Michal Marek suggested.
Masahiro Yamada (2):
kbuild: merge bounds.h and asm-offsets.h rules
kbuild: remove redundant line from bounds.h/asm-offsets.h
Kbuild | 61 +++++++++++++++++++++----------------------------------------
1 file changed, 21 insertions(+), 40 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-05 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 6:57 Masahiro Yamada [this message]
2015-01-05 6:57 ` [PATCH v2 1/2] kbuild: merge bounds.h and asm-offsets.h rules Masahiro Yamada
2015-01-05 6:57 ` [PATCH v2 2/2] kbuild: remove redundant line from bounds.h/asm-offsets.h Masahiro Yamada
2015-01-05 9:44 ` [PATCH v2 0/2] kbuild: Refactor ./Kbuild Michal Marek
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=1420441036-5289-1-git-send-email-yamada.m@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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).