linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: jikos@kernel.org
Cc: benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/9] HID: intel ISH: Cleanup patches
Date: Tue, 11 Sep 2018 16:44:12 -0700	[thread overview]
Message-ID: <20180911234421.10691-1-srinivas.pandruvada@linux.intel.com> (raw)

This series is a cleanup series only and help to abstract client API.

There are no functional changes.

Even Xu (6):
  hid: intel-ish-hid: ishtp: add helper function for driver data get/set
  hid: intel-ish-hid: use helper function for private driver data
    set/get
  hid: intel-ish-hid: ishtp: add helper functions for client buffer
    operation
  hid: intel-ish-hid: use helper function to access client buffer
  hid: intel-ish-hid: ishtp: add helper function for client search
  hid: intel-ish-hid: use helper function to search client id

Hong Liu (2):
  HID: intel-ish-hid: use resource-managed api
  HID: intel-ish-hid: using list_head for ipc write queue

Srinivas Pandruvada (1):
  HID: intel_ish-hid: Enhance API to get ring buffer sizes

 drivers/hid/intel-ish-hid/ipc/ipc.c           | 32 ++++----
 drivers/hid/intel-ish-hid/ipc/pci-ish.c       | 75 ++++++-------------
 drivers/hid/intel-ish-hid/ishtp-hid-client.c  | 41 ++++------
 drivers/hid/intel-ish-hid/ishtp/bus.c         | 52 +++++++++++++
 drivers/hid/intel-ish-hid/ishtp/bus.h         |  5 ++
 .../hid/intel-ish-hid/ishtp/client-buffers.c  | 49 ++++++++++++
 drivers/hid/intel-ish-hid/ishtp/client.c      | 24 ++++++
 drivers/hid/intel-ish-hid/ishtp/client.h      |  5 ++
 drivers/hid/intel-ish-hid/ishtp/ishtp-dev.h   |  2 +-
 9 files changed, 188 insertions(+), 97 deletions(-)

-- 
2.17.1


             reply	other threads:[~2018-09-11 23:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 23:44 Srinivas Pandruvada [this message]
2018-09-11 23:44 ` [PATCH 1/9] hid: intel-ish-hid: ishtp: add helper function for driver data get/set Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 2/9] hid: intel-ish-hid: use helper function for private driver data set/get Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 3/9] hid: intel-ish-hid: ishtp: add helper functions for client buffer operation Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 4/9] hid: intel-ish-hid: use helper function to access client buffer Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 5/9] hid: intel-ish-hid: ishtp: add helper function for client search Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 6/9] hid: intel-ish-hid: use helper function to search client id Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 7/9] HID: intel_ish-hid: Enhance API to get ring buffer sizes Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 8/9] HID: intel-ish-hid: use resource-managed api Srinivas Pandruvada
2018-09-11 23:44 ` [PATCH 9/9] HID: intel-ish-hid: using list_head for ipc write queue Srinivas Pandruvada
2018-09-24  9:21 ` [PATCH 0/9] HID: intel ISH: Cleanup patches 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=20180911234421.10691-1-srinivas.pandruvada@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).