mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: david@lang.hm
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Ingo Molnar <mingo@elte.hu>, Greg KH <gregkh@suse.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: removing existing working drivers via staging
Date: Tue, 27 Oct 2009 10:45:24 +0000	[thread overview]
Message-ID: <20091027104524.2cf3f9a5@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0910262119530.14994@asgard.lang.hm>

> this is exactly the 'wants to get rid of' category I mentioned being 
> concerned about below.

Why are you concerned, its dead, its defunct, nobody cares, nobody uses
it. The same is true of a lot of other junk drivers we have and need to
get rid of.

> I don't know what was decided at the kernel summit where this was 
> discussed, how easy is it supposed to be to drop drivers out of the 
> kernel?

If there is someone with the hardware its a trivial git command to put it
back and they can then maintain it, but I'm pretty sure that there won't
be anyone using this ancient hardware and I really doubt the code even
works after the big tty re-arrange.

There is a difference between ancient junk people care about (however
crazy) and stuff that is just dead and slowing real work (and I have
several serial drivers I want to bit bucket such as rio and esp)

  parent reply	other threads:[~2009-10-27 10:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  5:27 david
2009-10-15 16:33 ` Stefan Richter
2009-10-15 16:39   ` david
2009-10-15 16:47     ` Greg KH
2009-10-15 17:42       ` Bartlomiej Zolnierkiewicz
2009-10-15 17:49         ` Greg KH
2009-10-15 18:20           ` Bartlomiej Zolnierkiewicz
2009-10-15 18:46             ` Greg KH
2009-10-15 18:58               ` Bartlomiej Zolnierkiewicz
2009-10-15 19:02               ` david
2009-10-15 19:16                 ` Ingo Molnar
2009-10-15 19:38                   ` david
2009-10-15 19:47                     ` Stefan Richter
2009-10-15 19:57                       ` david
2009-10-27  4:23                         ` david
2009-10-27  5:22                           ` David Miller
2009-10-27  5:50                             ` david
2009-10-27 14:06                               ` Greg KH
2009-10-27 10:45                           ` Alan Cox [this message]
2009-10-16  7:40                     ` Ingo Molnar
2009-10-16  7:58                       ` Justin P. Mattock
2009-10-15 19:40                 ` Stefan Richter
2009-10-15 19:49                   ` david
2009-10-15 20:56                     ` Greg KH
2009-10-16  7:25                     ` Ingo Molnar
2009-10-15 18:44         ` Alan Cox
2009-10-15 19:24         ` David Miller
2009-10-17 17:27       ` Pavel Machek
2009-10-19  7:32         ` Ingo Molnar
2009-10-19  7:40           ` Greg KH

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=20091027104524.2cf3f9a5@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=david@lang.hm \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stefanr@s5r6.in-berlin.de \
    /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

all inboxes | Powered by JetHome®