public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Jiri Slaby <jirislaby@gmail.com>, Pavel Machek <pavel@suse.cz>,
	Christoph Hellwig <hch@lst.de>,
	Dominik Brodowski <linux@brodo.de>, Andi Kleen <ak@suse.de>,
	Adrian Bunk <bunk@stusta.de>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Nick Piggin <npiggin@suse.de>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Len Brown <len.brown@intel.com>
Subject: Re: Feature Removals for 2.6.25
Date: Wed, 13 Feb 2008 21:49:08 -0500	[thread overview]
Message-ID: <47B3AC24.5050605@tmr.com> (raw)
In-Reply-To: <1201829922.23523.68.camel@brick>

Harvey Harrison wrote:
> What:	CONFIG_FORCED_INLINING
> When:	June 2006
> Why:	Config option is there to see if gcc is good enough. (in january
>         2006). If it is, the behavior should just be the default. If it's not,
> 	the option should just go away entirely.
> Who:    Arjan van de Ven
> 
> Patch submitted to Arjan, maybe 2.6.25?
> ---------------------------

The "good enough" of gcc may be architecture dependent. Taking the 
option away where it works because somewhere else it doesn't may not be 
the optimal solution.


> Ping?
> What:   eepro100 network driver
> When:   January 2007
> Why:    replaced by the e100 driver
> Who:    Adrian Bunk <bunk@stusta.de>
> 
> ---------------------------

The last time we discussed this the team working on e100 said there were 
still issues (IIRC). Have they all been resolved?


> Ping?
> What:   sk98lin network driver
> When:   Feburary 2008
> Why:    In kernel tree version of driver is unmaintained. Sk98lin driver
> 	replaced by the skge driver. 
> Who:    Stephen Hemminger <shemminger@linux-foundation.org>
> 
> ---------------------------

We have been over this several times, and I thought someone had taken 
over the driver and was providing patches to put it in. Both skge and 
sky2 have been proposed as the replacement, people have reported 
problems with each. Suggest leaving this alone until the sk98lin 
actually needs work, then take it out. Problems in my problem system 
have been intermittent, take 4-40 hours to show and generate no errors, 
other than the driver thinks it's sending packets and the sniffer doesn't.


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2008-02-14  2:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:38 Feature Removals for 2.6.25 Harvey Harrison
2008-02-01  4:53 ` Arjan van de Ven
2008-02-01  5:18   ` Harvey Harrison
2008-02-01  6:33     ` Arjan van de Ven
2008-02-01  7:04       ` Harvey Harrison
2008-02-01  5:02 ` Feature Removals for 2.6.25 (USB driver api) Greg KH
2008-02-01  7:08 ` Feature Removals for 2.6.25 Stephen Hemminger
2008-02-02  1:29 ` Nick Piggin
2008-02-03 10:44 ` Feature Removals for 2.6.25 - old NCR53C9x driver Boaz Harrosh
2008-02-14  2:49 ` Bill Davidsen [this message]
2008-02-14  2:55   ` Feature Removals for 2.6.25 Stephen Hemminger
2008-02-14 18:16     ` Bill Davidsen
2008-02-14 18:24       ` Arjan van de Ven
2008-02-14 18:26         ` Christoph Hellwig
2008-02-14 23:20         ` David Newall
2008-02-15  3:27           ` Rene Herman

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=47B3AC24.5050605@tmr.com \
    --to=davidsen@tmr.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=harvey.harrison@gmail.com \
    --cc=hch@lst.de \
    --cc=jirislaby@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=npiggin@suse.de \
    --cc=pavel@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=shemminger@linux-foundation.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