linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elias Vanderstuyft <elias.vds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Elias Vanderstuyft
	<elias.vds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/2] Input: Improve handling of ff max_effects
Date: Thu, 17 Sep 2015 19:29:46 +0200	[thread overview]
Message-ID: <1442510988-3164-1-git-send-email-elias.vds@gmail.com> (raw)

This is a patch-set to improve the handling of max_effects in
ff-core and uinput.

Elias Vanderstuyft (2):
  Input: Document and check on implicitly defined FF_MAX_EFFECTS
  Input: uinput: Sanity check on ff_effects_max and EV_FF

 drivers/input/ff-core.c     |  5 +++++
 drivers/input/misc/uinput.c | 15 +++++++++++++++
 include/uapi/linux/input.h  |  8 ++++++++
 3 files changed, 28 insertions(+)

-- 
1.9.3

             reply	other threads:[~2015-09-17 17:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 17:29 Elias Vanderstuyft [this message]
2015-09-17 17:29 ` [PATCH 1/2] Input: Document and check on implicitly defined FF_MAX_EFFECTS Elias Vanderstuyft
2015-10-15  0:52   ` Dmitry Torokhov
     [not found] ` <1442510988-3164-1-git-send-email-elias.vds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-17 17:29   ` [PATCH 2/2] Input: uinput: Sanity check on ff_effects_max and EV_FF Elias Vanderstuyft
2015-10-15  0:52     ` Dmitry Torokhov
2015-11-05 22:34       ` Elias Vanderstuyft
     [not found]         ` <CADbOyBSeXDLzaSj=z3W2oMzg1DV3fP651wzLztUezSmf3B05qA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-06  1:32           ` Dmitry Torokhov
2015-11-08 17:37     ` [PATCH v2 " Elias Vanderstuyft
2015-12-19  1:50       ` Dmitry Torokhov

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=1442510988-3164-1-git-send-email-elias.vds@gmail.com \
    --to=elias.vds-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).