netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: jgarzik@intel.com, akpm@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] ixgb: fix ixgb_intr looping checks
Date: Fri, 05 Nov 2004 02:31:11 -0500	[thread overview]
Message-ID: <418B2C3F.60107@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0411021152220.24843-100000@isotope.jf.intel.com>

I'm OK with the patch, but it doesn't apply for me...

Can you resend against 2.6.10-rc1-bk14?

	Jeff

  parent reply	other threads:[~2004-11-05  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 20:45 [PATCH 2.6] ixgb: fix ixgb_intr looping checks Jesse Brandeburg
2004-11-02 20:50 ` Jesse Brandeburg
2004-11-05  7:31 ` Jeff Garzik [this message]
2004-11-08 22:50   ` Jesse Brandeburg
2004-11-08 23:10     ` Andrew Morton
2004-11-10 17:51       ` Jesse Brandeburg
2004-11-10 19:19         ` Andrew Morton

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=418B2C3F.60107@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@intel.com \
    --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).