From: Jeff Garzik <jgarzik@pobox.com>
To: Ganesh Venkatesan <ganesh.venkatesan@intel.com>
Cc: netdev <netdev@oss.sgi.com>
Subject: Re: [Patch 1/3 2.5] e1000: Configuration and user guide update
Date: Fri, 15 Oct 2004 12:32:36 -0400 [thread overview]
Message-ID: <416FFBA4.1080001@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0410150515070.31227-100000@isotope.jf.intel.com>
Ganesh Venkatesan wrote:
> diff -Nuarp old/linux-2.5/Documentation/networking/e1000.txt new/linux-2.5/Documentation/networking/e1000.txt
> --- old/linux-2.5/Documentation/networking/e1000.txt 2004-10-07 15:50:44.000000000 -0700
> +++ new/linux-2.5/Documentation/networking/e1000.txt 2004-10-07 15:51:15.000000000 -0700
all three patches in this series look OK, but are rejected due to
invalid patch header (see previous emails with details).
Your patch _must_ be apply-able with "patch -sp1 < patch"
Jeff
next prev parent reply other threads:[~2004-10-15 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 13:50 [Patch 1/3 2.5] e1000: Configuration and user guide update Ganesh Venkatesan
2004-10-15 16:32 ` Jeff Garzik [this message]
2004-10-18 10:22 ` [Patch 2.5 1/3] " Ganesh Venkatesan
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=416FFBA4.1080001@pobox.com \
--to=jgarzik@pobox.com \
--cc=ganesh.venkatesan@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).