From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Christopher Li <sparse@chrisli.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: Casting away noderef and address spaces?
Date: Tue, 23 Dec 2008 03:20:29 +0300 [thread overview]
Message-ID: <f19298770812221620s7ef34b9co55f1650220750b38@mail.gmail.com> (raw)
In-Reply-To: <1229990125.11628.0.camel@johannes>
On Tue, Dec 23, 2008 at 02:55, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Tue, 2008-12-23 at 02:53 +0300, Alexey Zaytsev wrote:
>
>> 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.
>
> Make sure to revert those that are in the tree now though, before the
> release.
>
By the way, are you sure the latest series you have sent is correct? To me it
seems that it does not make any warnings go away, and adds quite some more:
http://zaytsev.su/tmp/build.diff.txt
next prev parent reply other threads:[~2008-12-23 0:20 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
2008-12-22 23:55 ` Johannes Berg
2008-12-23 0:20 ` Alexey Zaytsev [this message]
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=f19298770812221620s7ef34b9co55f1650220750b38@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).