From: Manik Raina <manik@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ioctl conflicts
Date: Thu, 30 Aug 2001 15:04:48 +0530 [thread overview]
Message-ID: <3B8E08B8.F4856A47@cisco.com> (raw)
In-Reply-To: <20010828145304Z.haba@pdc.kth.se> <3B8DEF9D.26F7544D@cisco.com> <slrn9ortim.352.kraxel@bytesex.org>
If the parameters were the same, we would have the
same number. Even though they go different places,
we would have the same number mapping into different
ioctls. that doesn't look too good.
> The size of the argument has a different size, so they end up with
> different magic numbers because of that.
>
next prev parent reply other threads:[~2001-08-30 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 12:53 Size of pointers in sys_call_table? Harald Barth
2001-08-28 13:26 ` Brian Gerst
2001-08-28 14:30 ` Harald Barth
2001-08-28 16:17 ` Alan Cox
2001-08-29 0:49 ` Keith Owens
2001-08-29 23:26 ` Ralf Baechle
2001-08-30 7:47 ` ioctl conflicts Manik Raina
2001-08-30 8:16 ` Gerd Knorr
2001-08-30 9:31 ` David S. Miller
2001-08-30 9:34 ` Manik Raina [this message]
2001-08-30 8:20 ` Alan Cox
2001-08-30 8:30 ` David S. Miller
2001-08-30 9:00 ` Andreas Schwab
2001-08-30 9:14 ` Alan Cox
2001-08-30 9:29 ` David S. Miller
2001-08-30 9:15 ` Andreas Dilger
2001-09-03 1:06 ` Wichert Akkerman
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=3B8E08B8.F4856A47@cisco.com \
--to=manik@cisco.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