From: Jeff Garzik <jgarzik@pobox.com>
To: Kevin Curtis <kevin.curtis@farsite.co.uk>
Cc: netdev@oss.sgi.com, davem@redhat.com, jgarzik@redhat.com,
Dermot Smith <dermot.smith@farsite.co.uk>,
Steve Scott <steve.scott@farsite.co.uk>
Subject: Re: Update FarSync WAN driver in 2.4 and 2.6
Date: Thu, 27 May 2004 13:24:51 -0400 [thread overview]
Message-ID: <40B62463.2030605@pobox.com> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E25CD7E@general.hq.farsitecommunications.com>
Kevin Curtis wrote:
> Hi,
> can you please respond to this e-mail and let me know when we
> might expect to see our driver changes implemented in the 2.4 and 2.6
> Kernels.
Ok, I applied your update to both 2.4 and 2.6 kernels.
Jeff
prev parent reply other threads:[~2004-05-27 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:41 Update FarSync WAN driver in 2.4 and 2.6 Kevin Curtis
2004-05-27 17:24 ` Jeff Garzik [this message]
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=40B62463.2030605@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=dermot.smith@farsite.co.uk \
--cc=jgarzik@redhat.com \
--cc=kevin.curtis@farsite.co.uk \
--cc=netdev@oss.sgi.com \
--cc=steve.scott@farsite.co.uk \
/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).