From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree <devicetree@vger.kernel.org>
Subject: [PATCH 0/3] input / dt-bindings: Unify defining of evdev codes
Date: Sat, 12 Sep 2015 15:26:09 +0200 [thread overview]
Message-ID: <1442064372-3030-1-git-send-email-hdegoede@redhat.com> (raw)
Hi All,
Here is a patch-set to unify the defining of evdev codes between
uapi/linux/input.h and dt-bindings/input/input.h by using a single
shared file, rather then manually keeping things in sync.
The third patch is mainly included as an example using some new / extra
evcodes this makes available in dts files.
Assuming everyone involved likes this, I believe it is best for the
first 2 patches to be both merged to Dmitry's input tree, as the second
patch depends on the first one.
Regards,
Hans
next reply other threads:[~2015-09-12 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 13:26 Hans de Goede [this message]
2015-09-12 13:26 ` [PATCH 1/3] input: Add an input-event-codes header file Hans de Goede
2015-09-12 13:26 ` [PATCH 2/3] devicetree: bindings: use input-event-codes.h for evdev codes Hans de Goede
2015-09-15 11:24 ` Ian Campbell
2015-09-16 14:27 ` Hans de Goede
2015-09-16 14:40 ` Ian Campbell
2015-09-16 14:43 ` Hans de Goede
2015-09-17 11:00 ` Ian Campbell
[not found] ` <1442487617.18856.177.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2015-09-17 19:35 ` Hans de Goede
2015-09-17 20:00 ` Rob Herring
2015-09-17 20:04 ` Hans de Goede
[not found] ` <1442064372-3030-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-12 13:26 ` [PATCH 3/3] ARM: dts: sun4i: inet9f-rev03: Add support for game buttons / joysticks Hans de Goede
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=1442064372-3030-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@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).