From: Arnd Bergmann <arnd@arndb.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Ping Cheng <pingc@wacom.com>,
Chris Bagwell <chris@cnpbagwell.com>
Subject: Re: [RFC][PATCH] input: Introduce device information ioctl
Date: Tue, 7 Dec 2010 13:55:08 +0100 [thread overview]
Message-ID: <201012071355.08714.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTi=Av1N2URqpgrAUCreFoJXb6ZtEkkgp_Jo4BgRw@mail.gmail.com>
On Tuesday 07 December 2010, Kay Sievers wrote:
> >> Oh, how does that work? With the ioctl call, userspace has to supply
> >> the size it expects to be returned from the kernel. How does the
> >> kernel otherwise know how much it is allowed to copy to the user?
> >
> > The ioctl command number itself is calculated from the size of the
> > data that gets passed:
> >
> > #define EVIOCGDEVINFO _IOR('E', 0x09, struct input_devinfo)
> >
> > If struct input_devinfo ever changes (which it can, but should not),
> > the command changes as well.
>
> So unlike statet, it's not extensible, and this struct and this ioctl
> can never change?
Exactly. We have plenty of unused ioctl numbers free though.
Arnd
next prev parent reply other threads:[~2010-12-07 12:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 7:25 [RFC][PATCH] input: Introduce device information ioctl Henrik Rydberg
2010-12-07 9:16 ` Dmitry Torokhov
2010-12-07 10:48 ` Kay Sievers
2010-12-07 10:56 ` Dmitry Torokhov
2010-12-07 11:19 ` Kay Sievers
2010-12-07 12:44 ` Arnd Bergmann
2010-12-07 12:52 ` Kay Sievers
2010-12-07 12:52 ` Kay Sievers
2010-12-07 12:55 ` Arnd Bergmann [this message]
2010-12-07 12:40 ` Arnd Bergmann
2010-12-07 12:49 ` Kay Sievers
2010-12-07 16:51 ` Dmitry Torokhov
2010-12-07 19:57 ` Henrik Rydberg
2010-12-08 6:02 ` Dmitry Torokhov
2010-12-08 19:04 ` Henrik Rydberg
2010-12-09 9:25 ` Dmitry Torokhov
2010-12-07 16:22 ` Greg KH
2010-12-07 16:48 ` Dmitry Torokhov
2010-12-07 18:48 ` Ping Cheng
2010-12-07 18:48 ` Ping Cheng
2010-12-07 19:35 ` Dmitry Torokhov
2010-12-07 19:35 ` Dmitry Torokhov
2010-12-07 19:18 ` Chris Bagwell
2010-12-07 19:37 ` Dmitry Torokhov
2010-12-07 19:37 ` Dmitry Torokhov
2010-12-08 20:26 ` Valdis.Kletnieks
2010-12-08 20:37 ` Henrik Rydberg
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=201012071355.08714.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pingc@wacom.com \
--cc=rydberg@euromail.se \
/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.