linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fedora Kernel Team <kernel-team@fedoraproject.org>
To: Jiri Kosina <jikos@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	Niels Skou Olsen <nolsen@jabra.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: [PATCH 0/4] Quirks cleanup and hid-generic niceness
Date: Mon,  2 Oct 2017 22:18:46 +0200	[thread overview]
Message-ID: <20171002201850.13175-1-kernel-team@fedoraproject.org> (raw)

From: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Hi,

This is the series I was talking about earlier[1].

Basically, Jiri, I'd like to see 1-3 applied in for-next at your earliest
convenience, and we can discuss about 4/4 without any rush.

I have this in my local tree since June, but I made some late minute
changes before sending, though the tests showed they are fine (I wouldn't
mind a second pair of eyes on it).

I am pretty sure we can optimize the things more, but for now this should be
just fine and just convert the quirks mechanism in hid-core.
For instance, there is a second call of hid_lookup_quirk() in usbhid/hid-core.c
that I am not sure about the absolute need.

Niels, please have a look at this and tell me if you are OK to rebase your
series on top of it.

Cheers,
Benjamin


[1] https://patchwork.kernel.org/patch/9980443/

Benjamin Tissoires (4):
  HID: core: move the dynamic quirks handling in core
  HID: quirks: move the list of special devices into a quirk
  HID: core: move the list of ignored devices in hid-quirks.c
  HID: core: remove the absolute need of hid_have_special_driver[]

 drivers/hid/Makefile            |    2 +-
 drivers/hid/hid-core.c          |  925 ++---------------------------
 drivers/hid/hid-generic.c       |   68 ++-
 drivers/hid/hid-quirks.c        | 1242 +++++++++++++++++++++++++++++++++++++++
 drivers/hid/usbhid/Makefile     |    2 +-
 drivers/hid/usbhid/hid-core.c   |   10 +-
 drivers/hid/usbhid/hid-quirks.c |  401 -------------
 include/linux/hid.h             |   21 +-
 net/bluetooth/hidp/core.c       |    2 +-
 9 files changed, 1388 insertions(+), 1285 deletions(-)
 create mode 100644 drivers/hid/hid-quirks.c
 delete mode 100644 drivers/hid/usbhid/hid-quirks.c

-- 
2.9.5


             reply	other threads:[~2017-10-02 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 20:18 Fedora Kernel Team [this message]
     [not found] ` <20171002201850.13175-1-kernel-team-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy@public.gmane.org>
2017-10-02 20:18   ` [PATCH 1/4] HID: core: move the dynamic quirks handling in core Fedora Kernel Team
2017-10-02 20:23   ` [PATCH 0/4] Quirks cleanup and hid-generic niceness Benjamin Tissoires
2017-10-02 20:18 ` [PATCH 2/4] HID: quirks: move the list of special devices into a quirk Fedora Kernel Team
2017-10-02 20:18 ` [PATCH 3/4] HID: core: move the list of ignored devices in hid-quirks.c Fedora Kernel Team
2017-10-02 20:18 ` [PATCH 4/4] HID: core: remove the absolute need of hid_have_special_driver[] Fedora Kernel Team

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=20171002201850.13175-1-kernel-team@fedoraproject.org \
    --to=kernel-team@fedoraproject.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=nolsen@jabra.com \
    /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).