public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Lse-tech] [RFC] fork historic module
Date: Fri, 17 Dec 2004 17:52:38 +0100	[thread overview]
Message-ID: <41C30ED6.5010201@colorfullife.com> (raw)

Andi wrote:

>> +/* IOCTL numbers */
>> +/* If you add a new IOCTL number don't forget to update FH_MAXNR */
>> +#define FH_MAGIC	0x35
>> +#define FH_REGISTER	_IO(FH_MAGIC,0)
>> +#define FH_UNREGISTER	_IO(FH_MAGIC,1)
>
>Is this really unique? 32bit emulation currently needs unique ioctl numbers.
>  
>
Are there plans to fix that? Perhaps move the emulation callback into 
struct file?

--
    Manfred


             reply	other threads:[~2004-12-17 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 16:52 Manfred Spraul [this message]
2004-12-17 16:59 ` [Lse-tech] [RFC] fork historic module Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-12-17 14:58 Guillaume Thouvenin
2004-12-17 15:11 ` [Lse-tech] " Andi Kleen
2004-12-20  7:28   ` Guillaume Thouvenin
2004-12-17 17:39 ` Erich Focht

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=41C30ED6.5010201@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=ak@suse.de \
    --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