public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jon Smirl <jonsmirl@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mike Galbraith <efault@gmx.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Opinions on removing /proc/tty?
Date: Tue, 11 Jul 2006 15:03:32 -0700	[thread overview]
Message-ID: <20060711220332.GE663@kroah.com> (raw)
In-Reply-To: <20060708172047.GA23882@flint.arm.linux.org.uk>

On Sat, Jul 08, 2006 at 06:20:47PM +0100, Russell King wrote:
> On Sat, Jul 08, 2006 at 12:20:06PM -0400, Jon Smirl wrote:
> > I'll put together a patch making it mountable. Is there any specific
> > info that needs to be added to sysfs?
> 
> Adding info to the sysfs side of tty devices is rather fraught (or was
> last time I looked - I'd like to do exactly that with serial_core.)
> 
> Unfortunately, until it becomes easier (and maybe it recently has now
> that tty_register_device returns the class device struct), /proc/tty
> needs to stay.  But... I heard that Greg wants to remove struct
> class_device...

Yes I do want to remove it, but anything that you add to the
class_device will still work just fine, I'm not wanting to break
userspace tools anymore :)

And it should be pretty easy to do, now that we do return the
class_device that you need to have to add files to.

thanks,

greg k-h

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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  2:56 Opinions on removing /proc/tty? Jon Smirl
2006-07-08  5:30 ` Randy.Dunlap
     [not found]   ` <9e4733910607072256q65188526uc5cb706ec3ecbaee@mail.gmail.com>
2006-07-09  5:04     ` Randy.Dunlap
     [not found]       ` <9e4733910607082220v754a000ak7e75ae4042a5e595@mail.gmail.com>
2006-07-09  5:27         ` Randy.Dunlap
2006-07-09 10:07         ` Antonino A. Daplas
     [not found]           ` <9e4733910607090645l236f17f1sb9778f0fc6c6ca01@mail.gmail.com>
2006-07-09 17:35             ` Randy.Dunlap
2006-07-09 23:31               ` Antonino A. Daplas
     [not found]                 ` <9e4733910607091744k273a7351l16abbcc6ff8c4bbd@mail.gmail.com>
2006-07-11 22:01                   ` Greg KH
     [not found]                     ` <9e4733910607111532s3fc2bb52q3f0247a9f2289d4e@mail.gmail.com>
2006-07-13 18:37                       ` Greg KH
2006-07-08  7:40 ` Mike Galbraith
2006-07-08 14:12   ` Jon Smirl
2006-07-08 14:48     ` Alan Cox
2006-07-08 16:20       ` Jon Smirl
2006-07-08 17:20         ` Russell King
2006-07-11 22:03           ` Greg KH [this message]
2006-07-08 16:12     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2006-07-09  5:30 Albert Cahalan
2006-07-09 14:04 ` Jon Smirl
2006-07-09 16:23   ` Albert Cahalan
2006-07-09 17:00     ` Ray Lee
2006-07-09 17:08       ` Ray Lee
2006-07-09 19:26       ` Albert Cahalan
2006-07-09 19:31         ` Russell King
2006-07-09 19:57           ` Albert Cahalan
2006-07-10 14:02             ` Jan Engelhardt
2006-07-10 15:06               ` Albert Cahalan
2006-07-10 22:17                 ` Jan Engelhardt
2006-07-11  1:07                   ` Albert Cahalan
2006-07-11  1:48                     ` H. Peter Anvin

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=20060711220332.GE663@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=efault@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox