From: "Jörn Engel" <joern@logfs.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [PATCH 3/7] Improve alloc_percpu: expose percpu_modalloc and percpu_modfree
Date: Tue, 18 Nov 2008 10:44:40 +0100 [thread overview]
Message-ID: <20081118094439.GA17733@logfs.org> (raw)
In-Reply-To: <200811180854.52492.rusty@rustcorp.com.au>
On Tue, 18 November 2008 08:54:52 +1030, Rusty Russell wrote:
> On Tuesday 18 November 2008 00:17:13 Jörn Engel wrote:
> >
> > You didn't test the patches much, did you? :)
>
> No, not UP :) I'd spent over four hours on them, so I figured it was time to
> post them and get some concrete discussion.
Oh, absolutely. I just wish I could give a more substantial comment to
all this.
Jörn
--
A defeated army first battles and then seeks victory.
-- Sun Tzu
prev parent reply other threads:[~2008-11-18 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 5:48 [PATCH 3/7] Improve alloc_percpu: expose percpu_modalloc and percpu_modfree Rusty Russell
2008-11-17 13:47 ` Jörn Engel
2008-11-17 22:24 ` Rusty Russell
2008-11-18 9:44 ` Jörn Engel [this message]
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=20081118094439.GA17733@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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