From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Why does x86_64 support a SuSE-specific ioctl?
Date: 05 Oct 2002 14:20:43 +0100 [thread overview]
Message-ID: <1033824043.3425.0.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <p73adltqz9g.fsf@oldwotan.suse.de>
On Sat, 2002-10-05 at 05:35, Andi Kleen wrote:
> */
> diff -urN linux-2.4.18.tmp/include/asm-alpha/ioctls.h linux-2.4.18.SuSE/include/asm-alpha/ioctls.h
> --- linux-2.4.18.tmp/include/asm-alpha/ioctls.h Sat May 4 11:37:28 2002
> +++ linux-2.4.18.SuSE/include/asm-alpha/ioctls.h Sat May 4 11:37:56 2002
> @@ -92,6 +92,7 @@
> #define TIOCGSID 0x5429 /* Return the session ID of FD */
> #define TIOCGPTN _IOR('T',0x30, unsigned int) /* Get Pty Number (of pty-mux device) */
> #define TIOCSPTLCK _IOW('T',0x31, int) /* Lock/unlock Pty */
> +#define TIOCGDEV _IOR('T',0x32, unsigned int) /* Get real dev no below /dev/console */
>
Shouldn't these values be reserved in 2.5 before anything goes into 2.4
for this - the values finally used might be different
next prev parent reply other threads:[~2002-10-05 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.NEB.4.44.0210041654570.11119-100000@mimas.fachschaften.tu-muenchen.de.suse.lists.linux.kernel>
2002-10-05 4:35 ` Andi Kleen
2002-10-05 5:04 ` Jeff Garzik
2002-10-05 5:10 ` Andi Kleen
2002-10-05 13:21 ` Alan Cox
2002-10-05 15:19 ` TIOCGDEV Andi Kleen
2002-10-05 17:00 ` Why does x86_64 support a SuSE-specific ioctl? Miquel van Smoorenburg
2002-10-09 18:03 ` Miquel van Smoorenburg
2002-10-05 7:56 ` H. Peter Anvin
2002-10-05 15:00 ` Andi Kleen
2002-10-07 17:48 ` Marcelo Tosatti
2002-10-05 13:20 ` Alan Cox [this message]
2002-10-05 14:36 ` Andrea Arcangeli
2002-10-04 14:59 Adrian Bunk
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=1033824043.3425.0.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@suse.de \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®