All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	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:42:28 -0800	[thread overview]
Message-ID: <1229985748.22856.23.camel@brick> (raw)
In-Reply-To: <70318cbf0812221433y62197ec7y851f00fa5775f150@mail.gmail.com>

On Mon, 2008-12-22 at 14:33 -0800, Christopher Li 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?
> 

I'd use/test such a branch rather than scraping the mailing list for
useful bits.

Harvey


  reply	other threads:[~2008-12-22 22:42 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 [this message]
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=1229985748.22856.23.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.