From: "Christopher Li" <sparse@chrisli.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Sam Ravnborg <sam@ravnborg.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: Mon, 22 Dec 2008 17:25:49 -0800 [thread overview]
Message-ID: <70318cbf0812221725p583010d6u2c4cafb9d3215546@mail.gmail.com> (raw)
In-Reply-To: <1229992670.11628.4.camel@johannes>
On Mon, Dec 22, 2008 at 4:37 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Tue, 2008-12-23 at 03:20 +0300, Alexey Zaytsev wrote:
>
>> 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
>
> include/net/sch_generic.h:225:2: warning: label 'continue' already bound
>
> This, of course, shouldn't happen. I thought I'd fixed it, but who
> knows. I think it should all just be reverted :)
Hi,
Do you want to resend your change which revert the context changes?
Make it base on Josh's git's tree and I will merge your changes in my
branch.
It will take me a while to get up to speed with the git goodness.
I will start with merging Alexey's resend patches.
Chris
next prev parent reply other threads:[~2008-12-23 1:25 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
2008-12-23 0:35 ` Johannes Berg
2008-12-23 0:37 ` Johannes Berg
2008-12-23 1:25 ` Christopher Li [this message]
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=70318cbf0812221725p583010d6u2c4cafb9d3215546@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=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=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).