From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>, Ping Cheng <pinglinux@gmail.com>,
Jason Gerecke <killertofu@gmail.com>,
Przemo Firszt <przemo@firszt.eu>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH v3 0/7] Bluetooth Wacom merge into the USB driver
Date: Tue, 29 Jul 2014 14:42:58 -0400 [thread overview]
Message-ID: <1406659385-3256-1-git-send-email-benjamin.tissoires@redhat.com> (raw)
Hi guys,
so this patch series is intended to be applied on top of Dmitry's wacom branch.
This time, I had a closer look at the various moves, and checkpatch does not
complained on anything besides the "open brace { [which] should be on the
previous line".
In v3, the difference is that now, no functionality has been dropped thanks to
Przemo. The LEDs are working through the same API in BT and USB, and the OLEDs
has been unified. They use the same sysfs node, and the same scrambled API.
The only difference we have now is that BT expecta 1-bit images, while USB
4-bits images.
Przemo, I'll let you add your s-o-b line in 4/7.
Ping, I did not added your previous Acked-by (the patch set has been split since).
Feel free to comment on this part too :)
Cheers,
Benjamin
Benjamin Tissoires (6):
Input - wacom: prepare the driver to include BT devices
Input - wacom: handle Graphire BT tablets in wacom.ko
Input - wacom: handle Intuos 4 BT in wacom.ko
Input - wacom: Check for bluetooth protocol while setting OLEDs
Input - wacom: add copyright note and bump version to 2.0
HID: remove hid-wacom Bluetooth driver
Przemo Firszt (1):
Input - wacom: Remove passing id for wacom_set_report
drivers/hid/Kconfig | 10 +-
drivers/hid/Makefile | 3 +-
drivers/hid/hid-core.c | 2 -
drivers/hid/hid-wacom.c | 973 ------------------------------------------------
drivers/hid/wacom.h | 3 +
drivers/hid/wacom_sys.c | 169 +++++++--
drivers/hid/wacom_wac.c | 168 ++++++++-
drivers/hid/wacom_wac.h | 5 +
8 files changed, 323 insertions(+), 1010 deletions(-)
delete mode 100644 drivers/hid/hid-wacom.c
--
2.0.3
next reply other threads:[~2014-07-29 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 18:42 Benjamin Tissoires [this message]
2014-07-29 18:42 ` [PATCH v3 1/7] Input - wacom: prepare the driver to include BT devices Benjamin Tissoires
2014-07-29 18:43 ` [PATCH v3 2/7] Input - wacom: handle Graphire BT tablets in wacom.ko Benjamin Tissoires
2014-07-29 18:43 ` [PATCH v3 3/7] Input - wacom: handle Intuos 4 BT " Benjamin Tissoires
2014-07-29 18:43 ` [PATCH v3 4/7] Input - wacom: Check for bluetooth protocol while setting OLEDs Benjamin Tissoires
2014-07-29 22:53 ` Przemo Firszt
2014-07-31 15:56 ` Ping Cheng
2014-07-31 21:14 ` Przemo Firszt
2014-07-29 18:43 ` [PATCH v3 5/7] Input - wacom: Remove passing id for wacom_set_report Benjamin Tissoires
2014-07-29 18:43 ` [PATCH v3 6/7] Input - wacom: add copyright note and bump version to 2.0 Benjamin Tissoires
2014-08-05 15:05 ` [PATCH v4] " Benjamin Tissoires
2014-07-29 18:43 ` [PATCH v3 7/7] HID: remove hid-wacom Bluetooth driver Benjamin Tissoires
2014-07-31 19:18 ` Przemo Firszt
2014-07-31 19:32 ` Benjamin Tissoires
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=1406659385-3256-1-git-send-email-benjamin.tissoires@redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinglinux@gmail.com \
--cc=przemo@firszt.eu \
/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).