From: Pekka Enberg <penberg@kernel.org>
To: Xi Wang <xi.wang@gmail.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH RFC] sparse, llvm: simplify function generation
Date: Sat, 18 May 2013 10:36:27 +0300 [thread overview]
Message-ID: <CAOJsxLGWnOTLNX6HR3tymU6PQ7jsdEjimny1NNzi8Gzesd0ckQ@mail.gmail.com> (raw)
In-Reply-To: <1368774359-5475-1-git-send-email-xi.wang@gmail.com>
On Fri, May 17, 2013 at 10:05 AM, Xi Wang <xi.wang@gmail.com> wrote:
> Remove repeated code, such as get_func_type() vs sym_func_type(),
> pseudo_type() vs symbol_type().
>
> Fix generating variadic functions.
>
> Add a test case using printf().
>
> Cc: Pekka Enberg <penberg@kernel.org>
> Cc: Jeff Garzik <jgarzik@redhat.com>
> Signed-off-by: Xi Wang <xi.wang@gmail.com>
Applied, thanks!
prev parent reply other threads:[~2013-05-18 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 7:05 [PATCH RFC] sparse, llvm: simplify function generation Xi Wang
2013-05-18 7:36 ` Pekka Enberg [this message]
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=CAOJsxLGWnOTLNX6HR3tymU6PQ7jsdEjimny1NNzi8Gzesd0ckQ@mail.gmail.com \
--to=penberg@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-sparse@vger.kernel.org \
--cc=xi.wang@gmail.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).