public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, "Dr. Werner Fink" <werner@suse.de>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 1/1] console: add /proc/consoles
Date: Thu, 4 Nov 2010 06:17:32 -0700	[thread overview]
Message-ID: <20101104131732.GA10390@suse.de> (raw)
In-Reply-To: <4CD2836E.4090908@gmail.com>

On Thu, Nov 04, 2010 at 10:57:02AM +0100, Jiri Slaby wrote:
> On 11/03/2010 10:12 PM, Greg KH wrote:
> > On Wed, Nov 03, 2010 at 09:03:42PM +0100, Jiri Slaby wrote:
> >> On 11/03/2010 06:39 PM, Greg KH wrote:
> >>> On Wed, Nov 03, 2010 at 05:25:32PM +0100, Jiri Slaby wrote:
> >>>> Actually where this code should be in fs/proc/? Most of the /proc/* is
> >>>> handled elsewhere (fs/ mm/ kernel/). The rest is handled in specialized
> >>>> fs/proc/FILE.c.
> >>>
> >>> What's wrong with putting it into fs/proc/proc_tty.c?  That seems like
> >>> the most logical thing to me...
> >>
> >> consoles have little to do with ttys. Except ttys can be consoles.
> > 
> > And all consoles are ttys :)
> 
> Oh, they are not. Or maybe I'm missing something?

No, you are correct, I was wrong.

> >> To me
> >> it seems illogical to have info about netconsole, parallel consoles or
> >> early serials somewhere in /proc/tty/. That's why I moved the info from
> >> /proc/tty/ to /proc and the code from fs/proc/proc_tty.c to
> >> kernel/printk.c where consoles are managed.
> > 
> > Ok, how about fs/proc/proc_console.c instead?
> 
> Yes, this sounds good.

Great.

thanks,

greg k-h

      reply	other threads:[~2010-11-04 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1288798509-23550-1-git-send-email-jslaby@suse.cz>
2010-11-03 16:13 ` [PATCH 1/1] console: add /proc/consoles Greg KH
2010-11-03 16:16   ` Jiri Slaby
2010-11-03 16:22     ` Greg KH
2010-11-03 16:25       ` Jiri Slaby
2010-11-03 17:39         ` Greg KH
2010-11-03 20:03           ` Jiri Slaby
2010-11-03 21:12             ` Greg KH
2010-11-04  9:57               ` Jiri Slaby
2010-11-04 13:17                 ` Greg KH [this message]

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=20101104131732.GA10390@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=werner@suse.de \
    /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