From: Christopher Li <sparse@chrisli.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/2] Subject: Add a few GCC builtins
Date: Tue, 4 Aug 2009 14:35:06 -0700 [thread overview]
Message-ID: <70318cbf0908041435j59c33f64uc6f79b018884c8b2@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580908011023m73ec63b5rbc09862aeb31f847@mail.gmail.com>
On Sat, Aug 1, 2009 at 10:23 AM, Blue Swirl<blauwirbel@gmail.com> wrote:
> Sure. I removed the extra "Subject:" from the description.
Thanks, all two patches applied.
Chris
prev parent reply other threads:[~2009-08-04 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 9:28 [PATCH 2/2] Subject: Add a few GCC builtins Blue Swirl
2009-08-01 16:53 ` Christopher Li
2009-08-01 17:23 ` Blue Swirl
2009-08-04 21:35 ` Christopher Li [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=70318cbf0908041435j59c33f64uc6f79b018884c8b2@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=blauwirbel@gmail.com \
--cc=linux-sparse@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).