From: Daniel Drake <ddrake@brontes3d.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org, Josh Triplett <josh@freedesktop.org>
Subject: Re: [PATCH] Re: __attribute__ annotations and struct types
Date: Wed, 14 Feb 2007 16:02:07 -0500 [thread overview]
Message-ID: <1171486927.8554.0.camel@systems03.mmm.com> (raw)
In-Reply-To: <20070214201549.GB18753@chrisli.org>
On Wed, 2007-02-14 at 12:15 -0800, Christopher Li wrote:
> On Wed, Feb 14, 2007 at 03:01:54PM -0500, Daniel Drake wrote:
> > sparse doesn't like it:
> >
> > test.c:7:8: error: Trying to use reserved word '__attribute__'
> > as identifier
>
> Can you please try this:
>
> Chris
>
> Handle structure attribute.
Thanks for the quick response, works nicely!
--
Daniel Drake
Brontes Technologies, A 3M Company
next prev parent reply other threads:[~2007-02-14 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 20:01 __attribute__ annotations and struct types Daniel Drake
2007-02-14 20:15 ` [PATCH] " Christopher Li
2007-02-14 21:02 ` Daniel Drake [this message]
2007-02-14 21:05 ` Randy Dunlap
2007-02-23 2:23 ` Josh Triplett
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=1171486927.8554.0.camel@systems03.mmm.com \
--to=ddrake@brontes3d.com \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).