netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	john.ronciak@intel.com, ganesh.venkatesan@intel.com,
	mallikarjuna.chilakala@intel.com
Subject: Re: [patch 2.6.14-rc4] e1000: Driver version, white space, comments, device id & other
Date: Tue, 18 Oct 2005 22:24:34 -0400	[thread overview]
Message-ID: <4355AE62.7080605@pobox.com> (raw)
In-Reply-To: <10182005213103.13099@bilbo.tuxdriver.com>

John W. Linville wrote:
> From: Mallikarjuna R Chilakala <mallikarjuna.chilakala@intel.com>
> 
> Driver version, white space, comments, device id & other
> 
> Originally posted on 8/31 (and perhaps before)...I think it has not
> been committed because the patch from that posting was damaged.  I'm
> reposting to make sure it gets in... :-)
> 
> Signed-off-by: Mallikarjuna R Chilakala <mallikarjuna.chilakala@intel.com>
> Signed-off-by: Ganesh Venkatesan <ganesh.venkatesan@intel.com>
> Signed-off-by: John Ronciak <john.ronciak@intel.com>
> 
> Signed-off-by: John W. Linville <linville@tuxdriver.com>

patch is ok, but doesn't apply to 'upstream' branch of netdev-2.6.git, 
which has several e1000 patches in it.

	Jeff

  reply	other threads:[~2005-10-19  2:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  1:31 [patch 2.6.14-rc4] e1000: Driver version, white space, comments, device id & other John W. Linville
2005-10-19  2:24 ` Jeff Garzik [this message]
2005-10-19 14:31   ` John W. Linville
2005-10-19 14:40     ` [patch netdev-2.6] " John W. Linville
2005-10-20 14:07       ` Jeff Garzik

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=4355AE62.7080605@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mallikarjuna.chilakala@intel.com \
    --cc=netdev@vger.kernel.org \
    /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).