From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Grant Likely <glikely@secretlab.ca>,
Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
benjamin.tissoires@redhat.com
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)
Date: Wed, 24 Aug 2016 11:43:09 -0700 [thread overview]
Message-ID: <1472064189.28351.3.camel@linux.intel.com> (raw)
In-Reply-To: <CACxGe6v6pDisF9FpKPJrojGS7qUn13xUUd-Uydr7B1701Y4szg@mail.gmail.com>
On Wed, 2016-08-24 at 12:16 -0400, Grant Likely wrote:
> On Tue, Jul 5, 2016 at 8:42 AM, Grant Likely <glikely@secretlab.ca>
> wrote:
> >
> >
> > On 22/06/16 06:40, Srinivas Pandruvada wrote:
> > >
> > >
> > > Change log
> > > v2:
> > > - Overview in documentation show analogy with usbhid
> > > implementation
> > > - sparse errors for statics. Also pointed by Jiri
> > > - Clearly marking exported function header file. Clean up all
> > > exports
> > > unused inteface functions
> > > - Changed to tristate from boolean as pointed by Jiri:
> > > this required remove/unload functions
> > > - Prevent crash when ISH enabled on non supported platform
> > > - Break client.c to smaller part by seprating buffer allocations
> > > - move bus register/unregister to ishtp module
> > > - There is only one config symbol INTEL_ISH_HID, removed silent
> > > config for TRANSPORT and IPC
> >
> > Tested-by: Grant Likely <grant.likely@secretlab.ca>
> >
> > On an HP Spectre x360 laptop using v4.7-rc5.
>
> Hey Srinivas. Any progress on this patch series?
Unless someone has major objection, they can land up in 4.9.
They will go through two different trees, I can ping you once I see all
patches in linux-next.
Thanks,
Srinivas
>
> g.
next prev parent reply other threads:[~2016-08-24 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 5:40 [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-06-22 5:40 ` [PATCH v2 1/6] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-06-26 18:32 ` Jonathan Cameron
2016-06-27 15:24 ` Srinivas Pandruvada
2016-06-27 19:07 ` Jiri Kosina
2016-06-22 5:40 ` [PATCH v2 2/6] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-06-22 5:40 ` [PATCH v2 3/6] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-06-22 5:40 ` [PATCH v2 4/6] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-06-22 5:40 ` [PATCH v2 5/6] iio: hid-sensors: use asynchronous resume Srinivas Pandruvada
2016-06-22 5:40 ` [PATCH v2 6/6] hid: hid-sensor-hub: Add ISH quirk Srinivas Pandruvada
2016-06-23 22:00 ` [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-07-05 12:42 ` Grant Likely
2016-08-24 16:16 ` Grant Likely
2016-08-24 18:43 ` Srinivas Pandruvada [this message]
2016-08-24 21:14 ` Jiri Kosina
2016-08-24 21:23 ` Jonathan Cameron
2016-08-31 14:19 ` Grant Likely
2016-08-31 14:32 ` Srinivas Pandruvada
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=1472064189.28351.3.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=glikely@secretlab.ca \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.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).