All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, saw@saw.sw.com.sg,
	Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: [2.6 patch] the scheduled eepro100 removal
Date: Wed, 03 Jan 2007 10:10:50 +0100	[thread overview]
Message-ID: <459B731A.301@web.de> (raw)
In-Reply-To: <20070102215726.GC20714@stusta.de>

Adrian Bunk wrote:
> This patch contains the scheduled removal of the eepro100 driver.
> 

I'm sorry to disturb the schedule, but I'm not sure right now if this
pending issue of the e100 was meanwhile solved or declared a non-issue:

http://lkml.org/lkml/2006/9/8/105

Auke, can you confirm that it makes sense to re-test? IIRC, our private
thread ended without resolution after I discovered that the chip
revision makes the difference for me. Looked like it is either handled
incorrectly by e100 or screwed up on that board.

Jan

  parent reply	other threads:[~2007-01-03  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 21:57 [2.6 patch] the scheduled eepro100 removal Adrian Bunk
2007-01-03  0:07 ` Eric Piel
2007-01-03 22:14   ` Jesse Brandeburg
2007-01-03  9:10 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-20  0:06 Adrian Bunk
2007-03-25 14:58 Adrian Bunk
2007-03-28 22:17 ` Bill Davidsen
2007-03-28 22:26   ` Kok, Auke
2007-03-28 22:42     ` Jeff Garzik
2007-03-29  5:08       ` Yinghai Lu
2007-03-29  8:19         ` Roberto Nibali
2007-03-29 16:22           ` Brandeburg, Jesse
2007-03-30 16:40             ` Bill Davidsen

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=459B731A.301@web.de \
    --to=jan.kiszka@web.de \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.