From: Matthias Kaehlcke <mka@chromium.org>
To: "Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Michal Marek" <mmarek@suse.com>,
"Emese Revfy" <re.emese@gmail.com>,
"Kees Cook" <keescook@chromium.org>,
"Behan Webster" <behanw@converseincode.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
"Vinícius Tinti" <viniciustinti@gmail.com>,
"Kyeongmin Cho" <korea.drzix@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Grant Grundler <grundler@chromium.org>,
Michael Davidson <md@google.com>,
Greg Hackmann <ghackmann@google.com>,
Peter Foley <pefoley2@pefoley.com>
Subject: Re: [PATCH v3] kbuild: Add support to generate LLVM bitcode files
Date: Thu, 20 Apr 2017 11:04:06 -0700 [thread overview]
Message-ID: <20170420180406.GI128305@google.com> (raw)
In-Reply-To: <20170404172706.171971-1-mka@chromium.org>
El Tue, Apr 04, 2017 at 10:27:06AM -0700 Matthias Kaehlcke ha dit:
> From: Vinícius Tinti <viniciustinti@gmail.com>
>
> Add rules to kbuild in order to generate LLVM bitcode files with the .ll
> extension when using clang.
>
> # from c code
> CC=clang make kernel/pid.ll
>
> # from asm code
> CC=clang make arch/x86/kernel/preempt.ll
>
> From: Vinícius Tinti <viniciustinti@gmail.com>
> Signed-off-by: Vinícius Tinti <viniciustinti@gmail.com>
> Signed-off-by: Behan Webster <behanw@converseincode.com>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> ---
Ping, any comments on this patch?
Thanks
Matthias
next prev parent reply other threads:[~2017-04-20 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:27 [PATCH v3] kbuild: Add support to generate LLVM bitcode files Matthias Kaehlcke
2017-04-20 18:04 ` Matthias Kaehlcke [this message]
2017-04-21 5:02 ` Masahiro Yamada
2017-04-21 19:55 ` Matthias Kaehlcke
2017-04-23 6:57 ` Masahiro Yamada
2017-04-24 2:21 ` Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2014-07-23 12:00 [PATCH v2] kbuild: add " Tinti
2014-09-11 23:13 ` [PATCH v3] " Vinícius Tinti
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=20170420180406.GI128305@google.com \
--to=mka@chromium.org \
--cc=behanw@converseincode.com \
--cc=ghackmann@google.com \
--cc=grundler@chromium.org \
--cc=keescook@chromium.org \
--cc=korea.drzix@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=md@google.com \
--cc=mmarek@suse.com \
--cc=pefoley2@pefoley.com \
--cc=re.emese@gmail.com \
--cc=viniciustinti@gmail.com \
--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