From: Randy Dunlap <randy.dunlap@oracle.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
i4ldeveloper@listserv.isdn4linux.de, Karsten Keil <kkeil@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: so what *is* obsolete and removable?
Date: Mon, 16 Apr 2007 16:13:37 -0700 [thread overview]
Message-ID: <20070416161337.d59f2ea3.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4623FB0E.4080602@imap.cc>
On Tue, 17 Apr 2007 00:39:10 +0200 Tilman Schmidt wrote:
> Am 15.04.2007 22:55 schrieb Robert P. J. Day:
> > as i recall, the isdn4linux was *un*obsoleted, wasn't it?
>
> Actually, it wasn't.
>
> We *did* reach a consensus that isdn4linux is not obsolete in the
> accepted sense of the word, because there is no replacement for it
> so far.
>
> OTOH I have since submitted (twice, in fact) a patch that would remove
> the "(obsolete)" label from the Kconfig entry, but somehow nothing
> ever became of it. My submissions just linger in LKML, uncommented and
> unmerged.
Did you submit the patch to Andrew Morton?
Is the patch in the -mm patchset?
Did Karsten ack the patch?
If the patch is in -mm and it's not critical (like this subject),
then it probably won't be merged until after 2.6.21 is released...
> To sum it up, we agree that the "(obsolete)" label is wrong, but we
> won't remove it. I have no idea how to resolve that situation.
>
> What I do know is that it would be very wrong to remove isdn4linux,
> because it has an existing userbase with nowhere else to go.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-16 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 20:55 so what *is* obsolete and removable? Robert P. J. Day
2007-04-15 21:45 ` Jiri Slaby
2007-04-15 21:50 ` Jesper Juhl
2007-04-16 14:44 ` Robert P. J. Day
2007-04-16 14:58 ` Adrian Bunk
2007-04-16 22:39 ` Tilman Schmidt
2007-04-16 23:13 ` Randy Dunlap [this message]
2007-04-17 12:52 ` Tilman Schmidt
2007-04-17 13:40 ` Alan Cox
2007-04-17 15:03 ` Tilman Schmidt
2007-04-17 15:33 ` Alan Cox
2007-04-17 17:55 ` 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=20070416161337.d59f2ea3.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=tilman@imap.cc \
/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