netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Kevin Curtis <kevin.curtis@farsite.co.uk>
Cc: netdev@oss.sgi.com, davem@redhat.com
Subject: Re: Update FarSync WAN driver in 2.6
Date: Sun, 29 Feb 2004 13:53:19 -0500	[thread overview]
Message-ID: <4042351F.9070703@pobox.com> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E25CBF0@general.hq.farsitecommunications.com>

hum...  Patch looks OK to appy, but does not apply against the latest 
2.6.x kernel.

Also, it is possible to split your patch into two pieces:  one patch 
with nothing but indentation/whitespace cleanups, and the other patch 
with functional changes?

	Jeff

  reply	other threads:[~2004-02-29 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 11:02 Update FarSync WAN driver in 2.6 Kevin Curtis
2004-02-29 18:53 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-25 17:19 Kevin Curtis
2004-03-01 13:55 Kevin Curtis
2004-03-12 16:57 Kevin Curtis
2004-03-19  9:26 Kevin Curtis

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=4042351F.9070703@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@redhat.com \
    --cc=kevin.curtis@farsite.co.uk \
    --cc=netdev@oss.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).