From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christopher Li <sparse@chrisli.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-sparse@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Josh Triplett <josh@kernel.org>
Subject: Re: Casting away noderef and address spaces?
Date: Tue, 23 Dec 2008 02:53:17 +0300 [thread overview]
Message-ID: <f19298770812221553n5281505ex611e8e6f6fa1f0c2@mail.gmail.com> (raw)
In-Reply-To: <20081222225708.GA4074@uranus.ravnborg.org>
On Tue, Dec 23, 2008 at 01:57, Sam Ravnborg <sam@ravnborg.org> wrote:
>>
>> 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?
>
> Please do so. We need some progress on sparse and current maintainer
> seems to be occupied by other things at the moment.
>
> Sam
Hello.
How about?
http://git.zaytsev.su/git?p=sparse.git;a=shortlog;h=discuss
This branch holds the two patch collections* I recently sent to the
mailing list. I
think it includes every useful patch that does not break the kernel check, and
even some that do. ;)
The last time we spoke (yesterday) Josh was going to merge the patches really
soon. The idea was to merge everything except the context patches, make a
release, add the context patches, and wait for someone to fix them.
next prev parent reply other threads:[~2008-12-22 23:53 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
2008-12-22 22:42 ` Harvey Harrison
2008-12-22 22:57 ` Sam Ravnborg
2008-12-22 23:53 ` Alexey Zaytsev [this message]
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=f19298770812221553n5281505ex611e8e6f6fa1f0c2@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=sparse@chrisli.org \
--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).