From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Hopkins <sah@coraid.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AoE inclusion into 2.4.x
Date: Wed, 21 Apr 2004 13:51:51 -0400 [thread overview]
Message-ID: <4086B4B7.4080008@pobox.com> (raw)
In-Reply-To: <c6be8c22d61f39eeb861c900d5abd7fe@borf.com>
Sam Hopkins wrote:
> Greetings,
>
> I would like to offer our driver for inclusion into the 2.4 kernel.
> Marcelo suggested (strongly) that I make this request officially
> to the list.
>
> The driver code is available from:
>
> http://www.coraid.com/support/aoe-1.6.tar
>
> I'm now going to cheat and copy our prior correspondence. Please CC me
> on any comments / questions as I'm not a lkml subscriber.
Overall it seems reasonably clean, though the following combination
seems a bit silly:
if(access_ok(VERIFY_WRITE, arg, sizeof(long)))
if(!copy_to_user((long *) arg, &d->disk.ssize, sizeof (long)))
next prev parent reply other threads:[~2004-04-21 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 17:34 AoE inclusion into 2.4.x Sam Hopkins
2004-04-21 17:51 ` Jeff Garzik [this message]
2004-04-21 17:52 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-04-21 18:27 Sam Hopkins
2004-04-21 21:08 ` Marcelo Tosatti
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=4086B4B7.4080008@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sah@coraid.com \
/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