From: Alan Cox <alan@linux.intel.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC 0/3] A little console mystery...
Date: Wed, 17 Feb 2010 13:22:47 +0000 [thread overview]
Message-ID: <20100217131931.17289.68158.stgit@localhost.localdomain> (raw)
Anyone feeling inspired. These three patches move the console to use the
tty_port interface and refcounting. The first two work perfectly, the third
which we really need works beautifully except that it breaks mingetty/login
stuff.
[So not for the main kernel if you like using text consoles]
I have been staring at this problem for ages and I'm clearly missing something
silly because I've still not pinned down why mingetty etc break with the
third patch applied.
---
Alan Cox (3):
vt: Fix refcounting use
tty: Move the vt_tty field from the vc_data into the standard tty_port
tty: Make vt's have a tty_port
next reply other threads:[~2010-02-17 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 13:22 Alan Cox [this message]
2010-02-17 13:23 ` [PATCH 1/3] tty: Make vt's have a tty_port Alan Cox
2010-02-17 13:23 ` [PATCH 2/3] tty: Move the vt_tty field from the vc_data into the standard tty_port Alan Cox
2010-02-17 13:23 ` [PATCH 3/3] vt: Fix refcounting use Alan Cox
2010-02-17 15:39 ` Richard Kennedy
2010-02-17 16:31 ` 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=20100217131931.17289.68158.stgit@localhost.localdomain \
--to=alan@linux.intel.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;
as well as URLs for NNTP newsgroup(s).