LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tilman Schmidt <tilman@imap.cc>
Cc: David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, kkeil@suse.de,
	i4ldeveloper@listserv.isdn4linux.de, akpm@linux-foundation.org
Subject: Re: [PATCH] Remove "obsolete" label from ISDN4Linux (v3)
Date: Sun, 22 Apr 2007 16:17:08 +0100	[thread overview]
Message-ID: <20070422161708.54253ab7@the-village.bc.nu> (raw)
In-Reply-To: <462B712D.7070504@imap.cc>

> obsolete and correctly re-labelled as such. As for the && !HOTPLUG
> menace you keep touting, that might perhaps be applied to some of
> the individual hardware device drivers but certainly not to the

In my tree its just the drivers that still use pci_find_device.

> > Want to be on that. There is nobody maintaining it. That isn't a
> > sustainable situation so it will break.
> 
> Not sure I'm following you. There is an official maintainer, and
> although he's currently rather silent on this topic, there's no
> reason to believe he won't step up if there's actually some urgent
> maintaining to be done.

Well once it ends up && BROKEN perhaps patches will appear, or before
that. If not well the pain factor will resolve the problem.

> > No risk of deadlock. It'll progress to && BROKEN which will either cause
> > sufficient pain for someone to get off their arse and fix it, for enough
> > of a vendors users to get the vendor to do the work or for someone who
> > cares to pay a third party to do the work.
> 
> Do I sense some hidden agenda there?

No I'm speaking from experience - if a subsystem maintainer is too
busy/working on other projects and the subsystem stops working it
produces a rapid and sudden supply of new maintainers, unless nobody
cares in which case it can go in the bitbucket.

> The isdn4linux subsystem will not "progress" to BROKEN unless
> somebody pushes it there. 

It has drivers using functions that will soon be deleted. That isn't so
much as pushing more like getting fed up of pulling someone elses cart
along.


  reply	other threads:[~2007-04-22 15:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 11:43 any value to fixing apparent bugs in old ISDN4Linux? Robert P. J. Day
2007-01-15 13:57 ` Karsten Keil
2007-01-15 17:09 ` Tilman Schmidt
2007-01-15 17:17   ` Robert P. J. Day
2007-01-15 17:29     ` Karsten Keil
2007-02-21  0:29       ` [PATCH] Remove "obsolete" label from ISDN4Linux (was: any value to fixing apparent bugs in old ISDN4Linux?) Tilman Schmidt
2007-03-28 22:18       ` [Repost][PATCH] Remove "obsolete" label from ISDN4Linux Tilman Schmidt
2007-04-21 13:07       ` [PATCH] Remove "obsolete" label from ISDN4Linux (v3) Tilman Schmidt
2007-04-21 20:58         ` Alan Cox
2007-04-21 22:10           ` David Miller
2007-04-22 12:27             ` Tilman Schmidt
2007-04-22 12:58               ` Alan Cox
2007-04-22 14:29                 ` Tilman Schmidt
2007-04-22 15:17                   ` Alan Cox [this message]
2007-04-22 15:48                     ` Satyam Sharma
2007-04-22 16:20                       ` Alan Cox
2007-04-23 23:58                         ` Tilman Schmidt
2007-05-28 16:32       ` [PATCH] ISDN4Linux: fix maturity label (v4) Tilman Schmidt

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=20070422161708.54253ab7@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=i4ldeveloper@listserv.isdn4linux.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tilman@imap.cc \
    --subject='Re: [PATCH] Remove "obsolete" label from ISDN4Linux (v3)' \
    /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

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).