From: Pavel Roskin <proski@gnu.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Structures from -include are "weak"
Date: Sun, 08 Jul 2007 02:25:23 -0400 [thread overview]
Message-ID: <1183875923.13053.2.camel@gx> (raw)
In-Reply-To: <20070708060609.GE21668@ftp.linux.org.uk>
On Sun, 2007-07-08 at 07:06 +0100, Al Viro wrote:
> Gyah... So it is. We put the stuff from -include into builtin_scope
> and start the file scope only in __sparse().
>
> See if adding
...
> in parse.c:struct_union_enum_specifier() would fix all problems of that kind.
Yes, it's working like a charm! Tested on 3 projects: madwifi, at76_usb
and orinoco_usb - all are fine. Thank you!
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-07-08 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 3:32 Structures from -include are "weak" Pavel Roskin
2007-07-08 5:42 ` Al Viro
2007-07-08 6:06 ` Al Viro
2007-07-08 6:25 ` Pavel Roskin [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=1183875923.13053.2.camel@gx \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.