All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jon Smirl <jonsmirl@gmail.com>,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Greg KH <greg@kroah.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Clean up old names in tty code to current names
Date: Mon, 10 Jul 2006 16:21:47 +0100	[thread overview]
Message-ID: <20060710152146.GA18728@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200607101510.k6AFAWND006142@turing-police.cc.vt.edu>

On Mon, Jul 10, 2006 at 11:10:32AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 10 Jul 2006 16:19:06 BST, Alan Cox said:
> > Ar Llu, 2006-07-10 am 10:57 -0400, ysgrifennodd Jon Smirl:
> > > > A few apps do rely on /proc/tty/drivers for the major-minor
> > > > to device name mapping. /dev/vc/0 does not exist (unless
> > > > created manually) without devfs.
> > > 
> > > This is why I questioned if /proc/tty was really in use, it contains
> > > an entry that is obviously wrong for my system.
> > 
> > Which tools already know about. What is so hard to understand about the
> > idea that pointless random changes break stuff and don't fix things.
> 
> On the other hand, a case can be made that if userspace already knows about
> the fact the thing is totally broken

Maybe - what if userspace is looking up /dev/tty0 in /proc/tty/drivers
and happens to know that it's called /dev/vc/0, because it's working
around this known idiosyncrasy of the kernel ?  If you change tty/drivers
to be the more correct /dev/tty0, such a program would needlessly break.

> fixing it won't break anything.

How can you be certain - I think that's Alan's point (if it isn't,
that's my point.)  The answer is you can't, so in order to maintain
ABI compatibility (and yes, this *IS* part of the kernel ABI) it
must be left exactly as-is.

> The only case is that some *already* terminally broken stuff may break
> further.

That "terminally broken stuff" might just happen to work with today's
kernels.  Even so, that's no reason to pile in additional user-visible
changes which could potentially have adverse effects.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-07-10 15:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  4:11 [PATCH] Clean up old names in tty code to current names Jon Smirl
2006-07-10  4:54 ` Andrew Morton
2006-07-10  7:14 ` H. Peter Anvin
2006-07-10  9:44 ` Alan Cox
2006-07-10 12:41   ` Jon Smirl
2006-07-10 13:10     ` Alan Cox
2006-07-10 13:03       ` Jon Smirl
2006-07-10 13:12         ` CaT
2006-07-10 13:18           ` Jon Smirl
2006-07-10 13:43         ` Alan Cox
2006-07-10 14:07           ` Jon Smirl
2006-07-10 14:17             ` Jan Engelhardt
2006-07-10 14:37             ` Alan Cox
2006-07-10 14:42             ` Antonino A. Daplas
2006-07-10 14:57               ` Jon Smirl
2006-07-10 15:19                 ` Alan Cox
2006-07-10 15:10                   ` Valdis.Kletnieks
2006-07-10 15:21                     ` Russell King [this message]
2006-07-10 15:38                       ` Valdis.Kletnieks
2006-07-10 15:35                   ` Antonino A. Daplas
2006-07-10 15:54                     ` Jon Smirl
2006-07-10 16:04                       ` H. Peter Anvin
2006-07-10 22:14                       ` Jan Engelhardt
2006-07-10 18:13               ` Alistair John Strachan
2006-07-11 21:54             ` Greg KH
2006-07-11 21:52     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11  2:18 Albert Cahalan

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=20060710152146.GA18728@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=jonsmirl@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.