From: "Christopher Li" <sparse@chrisli.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-sparse@vger.kernel.org
Subject: Re: Casting away noderef and address spaces?
Date: Mon, 22 Dec 2008 14:33:10 -0800 [thread overview]
Message-ID: <70318cbf0812221433y62197ec7y851f00fa5775f150@mail.gmail.com> (raw)
In-Reply-To: <20081222213953.GN28946@ZenIV.linux.org.uk>
On Mon, Dec 22, 2008 at 1:39 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Works here (built from 8f208e215a531d2b32aec0428fd5eaa24ae3100b)...
>
> But yes, SYM_TYPEOF is a brittle mess, so whether that works or not
> is, er, version-dependent ;-/
Very strange. That is exactly what I have in my clean sparse git tree.
I just clone it a few minutes ago. It give me errors on your example.
On my clean tree, I need the attached patch to get it to work.
>
> I really ought to resurrect lazy-type-expressions branch...
>
Are you sure you don't have some of those bits left over on your
git tree? If you submit your lazy-type-expressions patch, I can help to
review it.
BTW, I am normally lazy enough that I am happy about just submitting
patches. On the other hand, I am tried of these sparse patches floating
around the mailing list. I can start a branch to merge the proper patches.
Maybe some thing like a development branch for sparse.
Is that some thing other people want?
Chris
next prev parent reply other threads:[~2008-12-22 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 5:36 Casting away noderef and address spaces? Rusty Russell
2008-12-22 20:06 ` Christopher Li
2008-12-22 20:57 ` Al Viro
2008-12-22 21:23 ` Christopher Li
2008-12-22 21:39 ` Al Viro
2008-12-22 22:33 ` Christopher Li [this message]
2008-12-22 22:42 ` Harvey Harrison
2008-12-22 22:57 ` Sam Ravnborg
2008-12-22 23:53 ` Alexey Zaytsev
2008-12-22 23:55 ` Johannes Berg
2008-12-23 0:20 ` Alexey Zaytsev
2008-12-23 0:35 ` Johannes Berg
2008-12-23 0:37 ` Johannes Berg
2008-12-23 1:25 ` Christopher Li
2008-12-23 9:59 ` Johannes Berg
2008-12-24 8:34 ` Christopher Li
2008-12-23 2:14 ` Rusty Russell
2008-12-23 3:02 ` Christopher Li
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=70318cbf0812221433y62197ec7y851f00fa5775f150@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=viro@zeniv.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 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).