linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 24 Dec 2008 00:34:07 -0800	[thread overview]
Message-ID: <70318cbf0812240034kd5160a9iaa34f526c6d9c378@mail.gmail.com> (raw)
In-Reply-To: <1230026362.3046.4.camel@johannes>

On Tue, Dec 23, 2008 at 1:59 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
> Below. Or I can give it to you in git if you prefer. I still think we
> should redo this in some form so that annotations with different
> contexts can work properly, but I don't have time to take care of it
> right now.

Thanks for the patch. It applied cleanly. I am still checking weather I use git
properly. I will publish my git tree soon.

Chris

  reply	other threads:[~2008-12-24  8:34 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
2008-12-23  9:59                       ` Johannes Berg
2008-12-24  8:34                         ` Christopher Li [this message]
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=70318cbf0812240034kd5160a9iaa34f526c6d9c378@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).