From: Jeff Garzik <jgarzik@pobox.com>
To: ravinandan.arakali@s2io.com
Cc: "'Francois Romieu'" <romieu@fr.zoreil.com>,
netdev@oss.sgi.com, leonid.grossman@s2io.com,
raghavendra.koushik@s2io.com, rapuru.sriram@s2io.com
Subject: Re: [PATCH 2.6.9-rc2 4/8] S2io: hardware fixes
Date: Thu, 14 Oct 2004 10:47:21 -0400 [thread overview]
Message-ID: <416E9179.406@pobox.com> (raw)
In-Reply-To: <004a01c4b18b$36c1d660$6c10100a@S2IOtech.com>
no objections to this patch
next prev parent reply other threads:[~2004-10-14 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 1:14 [PATCH 2.6.9-rc2 4/8] S2io: hardware fixes Ravinandan Arakali
2004-10-14 14:47 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-08 23:30 Ravinandan Arakali
2004-10-09 0:11 ` Jeff Garzik
2004-10-09 0:34 ` Ravinandan Arakali
2004-10-09 0:31 ` Jeff Garzik
2004-10-10 3:24 ` Randy.Dunlap
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=416E9179.406@pobox.com \
--to=jgarzik@pobox.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@s2io.com \
--cc=rapuru.sriram@s2io.com \
--cc=ravinandan.arakali@s2io.com \
--cc=romieu@fr.zoreil.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).