From: Alan Cox <alan@redhat.com>
To: jgarzik@pobox.com (Jeff Garzik)
Cc: cw@sgi.com (Christopher Wedgwood),
marcelo@conectiva.com.br (Marcelo Tosatti),
alan@redhat.com (Alan Cox),
linux-kernel@vger.kernel.org, wildos@sgi.com
Subject: Re: [PATCH] (2.4.22-pre6 BK) New (IDE) driver: SGI IOC4
Date: Tue, 15 Jul 2003 20:13:41 -0400 (EDT) [thread overview]
Message-ID: <200307160013.h6G0Df906030@devserv.devel.redhat.com> (raw)
In-Reply-To: <3F149276.10600@pobox.com> from "Jeff Garzik" at Gor 15, 2003 07:47:02
> ITYM TASK_UNINTERRUPTIBLE, because you definitely don't handle being
> interrupted... :)
<2.4 IDE maintainer hat on>
Marcelo can you skip integrating this until we work through the questions
and a few others I'll write down tomorrow, so we get this merged nicely
</Hat>
next prev parent reply other threads:[~2003-07-15 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 22:27 [PATCH] (2.4.22-pre6 BK) New (IDE) driver: SGI IOC4 Christopher Wedgwood
2003-07-15 23:47 ` Jeff Garzik
2003-07-16 0:13 ` Alan Cox [this message]
2003-07-17 12:26 ` Alan Cox
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=200307160013.h6G0Df906030@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=cw@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=wildos@sgi.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;
as well as URLs for NNTP newsgroup(s).