From: Andrew Morton <akpm@linux-foundation.org>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [RFC Patch] kbuild: implement "make foo.s_c"
Date: Thu, 3 Sep 2009 22:38:09 -0700 [thread overview]
Message-ID: <20090903223809.7e303e6c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090904053233.4396.85814.sendpatchset@localhost.localdomain>
On Fri, 4 Sep 2009 01:30:06 -0400 Amerigo Wang <amwang@redhat.com> wrote:
> This patch implements "make path/to/file.s_c", where
> "file.s_c" is a file contains both asm and C code, this
> is helpful for people to do debugging at asm level.
Try
make path/to/file.lst
:)
next prev parent reply other threads:[~2009-09-04 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 5:30 [RFC Patch] kbuild: implement "make foo.s_c" Amerigo Wang
2009-09-04 5:38 ` Andrew Morton [this message]
2009-09-04 5:56 ` Amerigo Wang
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=20090903223809.7e303e6c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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).