public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jeff@garzik.org
Cc: jengelh@linux01.gwdg.de, kkeil@suse.de, kai.germaschewski@gmx.de,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ISDN: mark as 32-bit only
Date: Mon, 02 Oct 2006 13:37:15 -0700 (PDT)	[thread overview]
Message-ID: <20061002.133715.63105344.davem@davemloft.net> (raw)
In-Reply-To: <45208D82.8010606@garzik.org>

From: Jeff Garzik <jeff@garzik.org>
Date: Sun, 01 Oct 2006 23:54:42 -0400

> Jan Engelhardt wrote:
> >> Tons of ISDN drivers cast pointers to/from 32-bit values, which just
> >> won't work on 64-bit.
> > 
> > Should not that be fixed instead of restricting isdn to 32bit?
> 
> It hasn't been fixed in many years, and I don't see anyone stepping up 
> to the plate, even with my current trolling...  :)
> 
> > Though this is probably the best temporary workaround until someone can 
> > fix up all the "tons".
> 
> I have a better workaround, I think.

I totally agree with Jeff.  The ISDN layer is effectively unmaintained
and the vast majority of the ISDN work that does actually occur is
done out-of-tree.

If someone cares enough about the ISDN layer, they can make changes
after Jeff's goes in to reduce the protection to a per-driver basis.

But right now, blocking this whole unmaintained pile of poo on 64-bit
is the best starting point.

We're talking about effectively an 8 year old code base that hasn't
been touched much at all during that time.  Let's be honest about the
situation.  The only subsystem that is more unmaintained and gathering
dust is probably the ftape layer :-)



  reply	other threads:[~2006-10-02 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 15:21 [PATCH] ISDN: mark as 32-bit only Jeff Garzik
2006-10-01 18:08 ` Jan Engelhardt
2006-10-02  3:54   ` Jeff Garzik
2006-10-02 20:37     ` David Miller [this message]
2006-10-02 22:04       ` Alan Cox
2006-10-01 20:53 ` Alan Cox
2006-10-01 23:47 ` Alan Cox
2006-10-02  9:31   ` Karsten Keil
2006-10-02  9:26 ` Karsten Keil
2006-10-02  9:46 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-10-01 23:24 Tilman Schmidt
2006-10-02  0:10 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=20061002.133715.63105344.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kai.germaschewski@gmx.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.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