From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Aniroop Mathur <aniroop.mathur@gmail.com>
Cc: David Herrmann <dh.herrmann@gmail.com>,
Aniroop Mathur <a.mathur@samsung.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: evdev - add ioctl cmd EVIOCGBUFSIZE to get buffer size
Date: Fri, 8 Jan 2016 20:13:46 +0000 [thread overview]
Message-ID: <20160108201346.6a6694e2@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CADYu30_KWWELgNM4a0Lyd_AoewpmhizuxJxXJSXzoGSF5YFOZg@mail.gmail.com>
> During system boot up, user space buf size is fixed, it cannot be
> resized later and we cannot choose by hit&trial.
> struct input_event* mBuffer = new input_event[mBuf];
Who says that won't change ? Imagine a future case where plugging in a
device changes the buffer size ?
Alan
next prev parent reply other threads:[~2016-01-08 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 15:23 [PATCH] Input: evdev - add ioctl cmd EVIOCGBUFSIZE to get buffer size Aniroop Mathur
2016-01-08 15:29 ` David Herrmann
2016-01-08 19:53 ` Aniroop Mathur
2016-01-08 20:13 ` One Thousand Gnomes [this message]
2016-01-08 20:20 ` Aniroop Mathur
2016-01-08 20:33 ` One Thousand Gnomes
2016-01-08 20:51 ` Aniroop Mathur
2016-01-08 21:02 ` Dmitry Torokhov
2016-01-08 22:16 ` Aniroop Mathur
2016-01-08 22:27 ` Dmitry Torokhov
2016-01-08 22:43 ` Aniroop Mathur
2016-01-09 16:21 ` Aniroop Mathur
2016-01-09 18:51 ` Dmitry Torokhov
2016-01-09 23:03 ` Aniroop Mathur
2016-01-10 22:43 ` Peter Hutterer
2016-01-11 18:13 ` Aniroop Mathur
2016-01-11 23:46 ` Dmitry Torokhov
2016-01-12 7:14 ` Aniroop Mathur
2016-01-12 0:21 ` Peter Hutterer
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=20160108201346.6a6694e2@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=a.mathur@samsung.com \
--cc=aniroop.mathur@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).