From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
viro@parcelfarce.linux.theplanet.co.uk, Andi Kleen <ak@suse.de>,
Miquel van Smoorenburg <miquels@cistron.nl>
Subject: Re: [PATCH] fix tiocgdev 32/64bit emul
Date: Sun, 21 Mar 2004 20:57:58 +0100 [thread overview]
Message-ID: <405DF3C6.8050508@gmx.net> (raw)
In-Reply-To: <20040321185538.A10504@infradead.org>
Christoph Hellwig wrote:
> On Sun, Mar 21, 2004 at 07:50:23PM +0100, Carl-Daniel Hailfinger wrote:
>
>>>Isn't that SuSE's strange ioctl hack that has been rejected for mainline
>>>multiple times? why does x86_64 have an emulation for it if the ioctl
>>>isn't implemented anyway?
>>
>>Since this pops up from time to time, please let me explain what TIOCGDEV
>>does (if you know already, feel free to scoll to the end) and ask for
>>alternative solutions.
>
>
> Oh, I know what it does. Have you ever looked at Al's rawconsole patch
> that he coded up exactly in response to that hack?
>
> ftp://ftp.linux.org.uk/pub/people/viro/X0-rawconsole-B5
No. It was never announced on lkml, so I couldn't know of its existence.
Andi, Miquel: is the rawconsole patch usable for blogd?
Christoph: Have you looked at my question regarding
/sys/class/tty/console/dev ?
Regards,
Carl-Daniel
next prev parent reply other threads:[~2004-03-21 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 6:24 linguist
2004-03-21 16:45 ` [PATCH] fix tiocgdev 32/64bit emul Jeff Garzik
2004-03-21 16:57 ` Christoph Hellwig
2004-03-21 18:50 ` Carl-Daniel Hailfinger
2004-03-21 18:55 ` Christoph Hellwig
2004-03-21 19:57 ` Carl-Daniel Hailfinger [this message]
2004-03-21 20:02 ` Christoph Hellwig
2004-03-21 20:17 ` Carl-Daniel Hailfinger
2004-03-21 20:26 ` Christoph Hellwig
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=405DF3C6.8050508@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=ak@suse.de \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®