From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/next] add %.c->%.i and %.c->%.s rules
Date: Sun, 14 Jun 2009 17:11:41 +0200 [thread overview]
Message-ID: <20090614151141.GL22102@game.jcrosoft.org> (raw)
In-Reply-To: <1244991828-22250-1-git-send-email-vapier@gentoo.org>
On 11:03 Sun 14 Jun , Mike Frysinger wrote:
> The Linux kernel has some helper rules which allow you to quickly produce
> some of the intermediary files from C source. Specifically, you can
> create .i files which is the preprocessed output and you can create .s
> files which is the assembler output. This is useful when you are trying
> to track down header/macro expansion errors or inline assembly errors.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
I've not seen this this way
but yes ack
Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Best Regards,
J.
next prev parent reply other threads:[~2009-06-14 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 15:03 [U-Boot] [PATCH/next] add %.c->%.i and %.c->%.s rules Mike Frysinger
2009-06-14 15:11 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-06-14 21:37 ` Wolfgang Denk
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=20090614151141.GL22102@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=u-boot@lists.denx.de \
/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