From: David Gibson <david@gibson.dropbear.id.au>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Andrew Morton <akpm@osdl.org>,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix sparse parse error in lppaca.h
Date: Wed, 18 Jan 2006 13:55:54 +1100 [thread overview]
Message-ID: <20060118025554.GI762@localhost.localdomain> (raw)
In-Reply-To: <1137544465.4757.13.camel@serpentine.pathscale.com>
On Tue, Jan 17, 2006 at 04:34:25PM -0800, Bryan O'Sullivan wrote:
> sparse can't parse a struct definition in include/asm-powerpc/lppaca.h,
> even though gcc can accept it. The form looks like this:
>
> struct __attribute__((whatever)) foo { };
>
> An equivalent that both gcc and sparse can handle is
>
> struct foo { } __attribute__((whatever));
>
> This is the only definition of this type in the tree, and fixing it is
> easier than fixing sparse.
>
> Signed-off-by: Bryan O'Sullivan <bos@serpentine.com>
Oops.
Acked-by: David Gibson <david@gibson.dropbear.id.au>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2006-01-18 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 0:34 [PATCH] Fix sparse parse error in lppaca.h Bryan O'Sullivan
2006-01-18 2:55 ` David Gibson [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=20060118025554.GI762@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=bos@serpentine.com \
--cc=linux-kernel@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).