netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Leonid Grossman'" <leonid.grossman@s2io.com>,
	"'Jeff Garzik'" <jgarzik@pobox.com>
Cc: <netdev@oss.sgi.com>, <raghavendra.koushik@s2io.com>
Subject: RE: Patch submission for S2io Xframe driver to 2.6 kernel
Date: Mon, 30 Aug 2004 10:25:01 -0700	[thread overview]
Message-ID: <000a01c48eb6$489dcdf0$9d10100a@S2IOtech.com> (raw)
In-Reply-To: <200408290553.i7T5r0qG010550@guinness.s2io.com>

The comments are being addressed. But since Koushik is in
transition from Bangalore to Cupertino and the associated 
travel preparation, there may be some delay in the next 
submission.
In addition to the comments, we are trying to include 
additional code required for 32-bit systems.
Currently we are targeting middle of next week for the
next submission.

Ravi


-----Original Message-----
From: Leonid Grossman [mailto:leonid.grossman@s2io.com]
Sent: Saturday, August 28, 2004 10:53 PM
To: 'Jeff Garzik'; ravinandan.arakali@s2io.com
Cc: netdev@oss.sgi.com; raghavendra.koushik@s2io.com
Subject: RE: Patch submission for S2io Xframe driver to 2.6 kernel


Hi Ravi,
Please try to address the comments in real time, it's probably better to
submit a follow-up rather than waiting for more comments... 
Also - are Koushik and Sriram in Cupertino next week?
Cheers ,  Leonid

> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@pobox.com] 
> Sent: Saturday, August 28, 2004 4:37 PM
> To: ravinandan.arakali@s2io.com
> Cc: netdev@oss.sgi.com; leonid.grossman@s2io.com; 
> raghavendra.koushik@s2io.com
> Subject: Re: Patch submission for S2io Xframe driver to 2.6 kernel
> 
> is there a follow-up patch addressing the comments ?
> 

  reply	other threads:[~2004-08-30 17:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14  0:19 Patch submission for S2io Xframe driver to 2.6 kernel Ravinandan Arakali
2004-08-14  4:27 ` TCP hardware assists Leonid Grossman
2004-08-21  6:21 ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
2004-08-21 23:43 ` Francois Romieu
2004-08-28 23:36 ` Jeff Garzik
2004-08-29  5:53   ` Leonid Grossman
2004-08-30 17:25     ` Ravinandan Arakali [this message]
2004-09-13 17:09   ` Ravinandan Arakali
2004-09-17  0:38     ` Jeff Garzik
2004-09-17  0:53       ` Ravinandan Arakali
2004-09-17  0:52         ` Jeff Garzik
2004-09-17  3:07           ` Randy.Dunlap
2004-09-28  0:42           ` Ravinandan Arakali
2004-09-28  3:54             ` Randy.Dunlap
2004-09-28 15:05             ` Jeff Garzik
2004-09-28 17:13               ` Ravinandan Arakali
2004-10-06 20:14               ` Ravinandan Arakali
2004-10-06 20:09                 ` Jeff Garzik
2004-10-06 20:20                   ` Francois Romieu
2004-10-06 22:52                     ` Jeff Garzik
2004-10-07  1:04                       ` [PATCH 2.6.9-rc2 1/8] S2io: cosmetic changes Ravinandan Arakali
2004-09-17  3:58     ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2004-09-13 22:45 Ravinandan Arakali

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='000a01c48eb6$489dcdf0$9d10100a@S2IOtech.com' \
    --to=ravinandan.arakali@s2io.com \
    --cc=jgarzik@pobox.com \
    --cc=leonid.grossman@s2io.com \
    --cc=netdev@oss.sgi.com \
    --cc=raghavendra.koushik@s2io.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).