From: Rusty Russell <rusty@rustcorp.com.au>
To: tj@home-tj.org
Cc: mochel@osdl.org,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH] Per-device parameter support
Date: Mon, 25 Oct 2004 14:21:57 +1000 [thread overview]
Message-ID: <1098678117.8098.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20041023042024.GA3456@home-tj.org>
On Sat, 2004-10-23 at 13:20 +0900, tj@home-tj.org wrote:
> Hello,
>
> I rewrote the document, debugged and splitted devparam patch. I'm
> attaching the document in this mail and posting 16 patches
> (dp_01 - dp_16) which are against Linus's bk tree as of today.
Hi TJ,
Love the idea: thanks for doing this work! I'm reviewing the patches
themselves now, but I'll mainly concentrate on your moduleparam changes
which I'm not sure are necessary.
Cheers,
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2004-10-25 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 4:20 [RFC/PATCH] Per-device parameter support tj
2004-10-25 4:21 ` Rusty Russell [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=1098678117.8098.7.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=tj@home-tj.org \
/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