From: Jeff Garzik <jgarzik@pobox.com>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: "Jens Axboe (E-mail)" <axboe@suse.de>,
"Marcelo Tosatti (E-mail)" <marcelo@conectiva.com.br>,
"Lkml (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: cciss updates for 2.4.22
Date: Thu, 31 Jul 2003 10:15:20 -0400 [thread overview]
Message-ID: <3F292478.6040504@pobox.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF104052AC9@cceexc23.americas.cpqcorp.net>
Miller, Mike (OS Dev) wrote:
> The attached tarball contains 2 patches. The first is an author change for the cciss driver. The second resolves an issue when sharing IRQs with another controller. The patches have been built & tested against 2.4.22-pre9. They can be installed in any order.
> More to come.
Mike, you should consider sending one-patch-per-email. This makes it
much easier for Marcelo to use standard scripts to quickly and easily
apply your patches.
For the record, the patches look ok to me too.
Jeff
next prev parent reply other threads:[~2003-07-31 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 23:14 cciss updates for 2.4.22 Miller, Mike (OS Dev)
2003-07-31 12:15 ` Jens Axboe
2003-07-31 14:15 ` Jeff Garzik [this message]
2003-07-31 15:22 ` Jens Axboe
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=3F292478.6040504@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mike.miller@hp.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