From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org, Ray Strode <halfline@gmail.com>,
Kay Sievers <kay@vrfy.org>,
David Herrmann <dh.herrmann@gmail.com>,
Lennart Poettering <lennart@poettering.net>,
Werner Fink <werner@suse.de>
Subject: Re: [PATCH] tty: Add sysfs symlink for console name->tty device
Date: Fri, 28 Feb 2014 19:40:43 -0500 [thread overview]
Message-ID: <53112C8B.2000504@hurleysoftware.com> (raw)
In-Reply-To: <20140301003549.GB31852@kroah.com>
On 02/28/2014 07:35 PM, Greg Kroah-Hartman wrote:
> On Wed, Feb 26, 2014 at 09:40:51AM -0500, Peter Hurley wrote:
>> Enable a user-space process to discover the underlying tty device
>> for a console, if one exists, and when the tty device is later
>> created or destroyed.
>
> What userspace code has been tested with this change?
Every existing distro + personal copies going back 42 versions.
No breakage. ;)
>> Add sysfs symlinks for registered consoles to their respective
>> devices in [sys/class,sys/devices/virtual]/tty/console.
>> Scan consoles at tty device (un)registration to handle deferred
>> console<->device (un)binding.
>
> I don't understand, what does userspace now look like in sysfs? Do we
> need Documentation/ABI/ updates here?
>
> And David has fixed up his original patch, which doesn't break plymouth,
> and I'll be taking that, so I don't see why this patch is needed.
Ok. I tried.
Regards,
Peter Hurley
prev parent reply other threads:[~2014-03-01 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 14:40 [PATCH] tty: Add sysfs symlink for console name->tty device Peter Hurley
2014-02-27 11:13 ` Kay Sievers
2014-02-27 13:31 ` Peter Hurley
2014-02-27 13:36 ` Kay Sievers
2014-02-27 14:00 ` Peter Hurley
2014-03-01 0:35 ` Greg Kroah-Hartman
2014-03-01 0:40 ` Peter Hurley [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=53112C8B.2000504@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=dh.herrmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=halfline@gmail.com \
--cc=jslaby@suse.cz \
--cc=kay@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.