mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2 0/2] HID: hiddev: move hiddev's minor number and refactoring
Date: Fri,  3 Mar 2017 17:53:59 +0900	[thread overview]
Message-ID: <1488531241-18367-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

Chanes in v2:
- cp2112: tie in this series

- hiddev: rollback struct hiddev_list exported
          squash this patch in a seperate patch

Jaejoong Kim (2):
  HID: cp2112: use proper hidraw name with minor number
  HID: hiddev: reallocate hiddev's minor number

 drivers/hid/hid-core.c      |  2 +-
 drivers/hid/hid-cp2112.c    |  4 +++-
 drivers/hid/usbhid/hiddev.c | 15 ++++-----------
 include/linux/hid.h         |  1 -
 include/linux/hiddev.h      | 11 +++++++++++
 5 files changed, 19 insertions(+), 14 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-03-03  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  8:53 Jaejoong Kim [this message]
2017-03-03  8:54 ` [PATCH v2 1/2] HID: cp2112: use proper hidraw name with minor number Jaejoong Kim
2017-03-03  8:54 ` [PATCH v2 2/2] HID: hiddev: reallocate hiddev's " Jaejoong Kim
2017-03-21 14:25 ` [PATCH v2 0/2] HID: hiddev: move hiddev's minor number and refactoring Jiri Kosina

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=1488531241-18367-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

Powered by JetHome