From: Jaejoong Kim <climbbb.kim@gmail.com>
To: jikos@kernel.org, benjamin.tissoires@redhat.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, Jaejoong Kim <climbbb.kim@gmail.com>
Subject: [PATCH 0/2] HID: hiddev: move hiddev's minor number and refactoring
Date: Thu, 2 Mar 2017 22:45:28 +0900 [thread overview]
Message-ID: <1488462330-12349-1-git-send-email-climbbb.kim@gmail.com> (raw)
Hi all,
I found hiddev's minor number is always zero in struct hid_device. So,
store the minor number asked from usb core in struct hid_device.
This is my first approach.
But after reviewed from Bendjamin, he suggested that it would make sense
to store a minor number in struct hiddev like hidraw if it neeeded.
So, I move the minor number from hid_device to hiddev and do some refactoring
to access struct hiddev in hid-core
Jaejoong Kim (2):
HID: hiddev: move hiddev's minor number from struct hid_device to
hiddev
HID: hiddev: store hiddev's minor number when hiddev is connected
drivers/hid/hid-core.c | 2 +-
drivers/hid/usbhid/hiddev.c | 25 +++----------------------
include/linux/hid.h | 1 -
include/linux/hiddev.h | 24 ++++++++++++++++++++++++
4 files changed, 28 insertions(+), 24 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-02 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 13:45 Jaejoong Kim [this message]
2017-03-02 13:45 ` [PATCH 1/2] HID: hiddev: move hiddev's minor number from struct hid_device to hiddev Jaejoong Kim
2017-03-02 14:10 ` Benjamin Tissoires
2017-03-03 7:00 ` Kim Jaejoong
2017-03-03 14:47 ` kbuild test robot
2017-03-03 15:28 ` kbuild test robot
2017-03-02 13:45 ` [PATCH 2/2] HID: hiddev: store hiddev's minor number when hiddev is connected Jaejoong Kim
2017-03-02 14:13 ` Benjamin Tissoires
2017-03-03 7:05 ` Kim Jaejoong
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=1488462330-12349-1-git-send-email-climbbb.kim@gmail.com \
--to=climbbb.kim@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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