All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Re: TTY: tty_port questions
Date: Mon, 12 Mar 2012 12:15:32 +0100	[thread overview]
Message-ID: <4F5DDAD4.4060504@nod.at> (raw)
In-Reply-To: <20120312105312.665d2362@pyramind.ukuu.org.uk>

On 12.03.2012 11:53, Alan Cox wrote:
>> Another question, what is the purpose of tty_port->console?
>> It seems to have no user.
>
> So the tty_port layer can in future know about whether it is a console
> without a tty necessarily being present or referenceable.
>
>> Is tty_port really the right thing for a console driver like in the UML
>> case?
>
> It will be. In order to fix the tty locking mess we need to shove a lot
> of stuff whose lifetime is the lifetime of the physical port somewhere
> else - the tty_port is that structure.
>

"It will be" in terms of "not now"? ;-)

Thanks,
//richard

  reply	other threads:[~2012-03-12 11:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 22:26 TTY: tty_port questions Richard Weinberger
2012-03-10 22:51 ` Jiri Slaby
2012-03-10 23:21   ` Richard Weinberger
2012-03-11 11:01     ` Richard Weinberger
2012-03-12 10:26       ` Richard Weinberger
2012-03-12 10:53         ` Alan Cox
2012-03-12 11:15           ` Richard Weinberger [this message]
2012-03-12 11:48             ` Alan Cox
2012-03-24 23:20               ` Al Viro
2012-03-25 14:51                 ` Alan Cox
2012-03-25 15:14                   ` Richard Weinberger
2012-03-25 17:20                     ` Al Viro
2012-03-25 21:09                       ` Alan Cox
2012-03-25 18:31                   ` Al Viro
2012-03-25 21:06                     ` Alan Cox
2012-03-25 22:33                       ` Al Viro
2012-03-28 11:06                         ` Alan Cox

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=4F5DDAD4.4060504@nod.at \
    --to=richard@nod.at \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --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.