public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Jens Axboe <axboe@suse.de>,
	jeffrey.t.kirsher@intel.com,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] e1000 C style badness
Date: Wed, 18 Jan 2006 13:13:59 -0500	[thread overview]
Message-ID: <43CE8567.5040205@pobox.com> (raw)
In-Reply-To: <9e4733910601180953i11963df9n232cd8980c4bf7f2@mail.gmail.com>

Jon Smirl wrote:
> e1000 is failing the same way for me too. Chip is on the motherboard:
> Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
[...]
> I am using an old switch so I normally get a half duplex connection:
> Jan 18 10:14:25 jonsmirl kernel: e1000: eth0: e1000_watchdog_task: NIC
> Link is Up 100 Mbps Half Duplex
> I don't normally get the NETDEV up and changed notifications.

e1000 is failing for everybody :(  Looks like somewhere in this 40-patch 
behemoth, an "e1000 doesn't work anymore" change slipped in.

We'll get it fixed ASAP, even if it means reverting all those patches.

	Jeff



  reply	other threads:[~2006-01-18 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18  8:07 [PATCH] e1000 C style badness Jens Axboe
2006-01-18  8:37 ` Jens Axboe
2006-01-18 17:53   ` Jon Smirl
2006-01-18 18:13     ` Jeff Garzik [this message]
2006-01-18 18:20       ` Jens Axboe
2006-01-18 19:10         ` Jesse Brandeburg
2006-01-19  8:02           ` Jens Axboe
2006-01-21  6:52             ` Jesse Brandeburg
2006-01-21 11:42               ` Jens Axboe
     [not found] <5wgyi-18w-7@gated-at.bofh.it>
2006-01-18  8:56 ` Patrizio Bassi
2006-01-18  9:00   ` Jens Axboe
2006-01-18  9:02   ` Nick Piggin
2006-01-18 11:30     ` Patrizio Bassi

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=43CE8567.5040205@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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