From: Blue Swirl <blauwirbel@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: [PATCH 0/2] builtins and __bounded__ attribute
Date: Sat, 1 Aug 2009 12:28:34 +0300 [thread overview]
Message-ID: <f43fc5580908010228q6a2d7416l616816c3d104e181@mail.gmail.com> (raw)
1/2 is a resend of:
http://marc.info/?l=linux-sparse&m=123642492815770&w=2
Please CC me for any replies.
Blue Swirl (2):
Ignore attribute __bounded__, used by OpenBSD headers.
Add a few GCC builtins
lib.c | 25 ++++++++++++++++++++++---
parse.c | 2 ++
2 files changed, 24 insertions(+), 3 deletions(-)
reply other threads:[~2009-08-01 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f43fc5580908010228q6a2d7416l616816c3d104e181@mail.gmail.com \
--to=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).