From: Jonathan Cameron <jic23@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 5/7] iio: hid-sensors: use asynchronous resume
Date: Mon, 15 Aug 2016 16:49:51 +0100 [thread overview]
Message-ID: <6ee7950c-8602-a4a1-b87c-0e6a60752c50@kernel.org> (raw)
In-Reply-To: <CAKdAkRS-sVHqQ1tUZWVxNTfX5=ZxFzbCAxvsJPHV4=85mdEeRA@mail.gmail.com>
On 15/08/16 16:45, Dmitry Torokhov wrote:
> On Mon, Aug 15, 2016 at 7:52 AM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 15/08/16 15:07, Jonathan Cameron wrote:
>>> On 07/08/16 11:15, Jiri Kosina wrote:
>>>> On Sun, 7 Aug 2016, Srinivas Pandruvada wrote:
>>>>
>>>>> Some platforms power off sensor hubs during S3 suspend, which will require
>>>>> longer time to resume. This hurts system resume time, so resume
>>>>> asynchronously.
>>>>>
>>>>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>>>>
>>>> Jonathan, are you going to cherry-pick this patch from the series?
>>>> Alternatively, if you're okay with it, I can pull it in together with the
>>>> whole set with your Acked-by or Reviewed-by.
>>>>
>>> I'll take it via IIO. Got a bit of catching up to do (been on holiday)
>> Applied to the togreg branch of iio.git - initially pushed out as
>> testing for the autobuilders to play with it.
>> This one is not really connected to the others so makes sense to
>> take it separately.
>>
>> I'm out of my depth on the rest of the patches in this series
>> and don't have time to learn enough to follow them! Sorry I
>> can't help on that front.
>
> About this patch: me sees a new work, me does not see new calls to
> cancel_work_sync() or flush_work() anywhere, me gets worried.
>
> Thanks.
Good point.
Backed out for now...
Jonathan
>
next prev parent reply other threads:[~2016-08-15 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 9:25 [PATCH v4 0/7] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 1/7] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 2/7] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 3/7] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 4/7] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 5/7] iio: hid-sensors: use asynchronous resume Srinivas Pandruvada
2016-08-07 10:15 ` Jiri Kosina
2016-08-15 14:07 ` Jonathan Cameron
2016-08-15 14:52 ` Jonathan Cameron
2016-08-15 15:45 ` Dmitry Torokhov
2016-08-15 15:49 ` Jonathan Cameron [this message]
2016-08-15 16:42 ` Srinivas Pandruvada
2016-08-15 17:14 ` Dmitry Torokhov
2016-08-15 17:29 ` Srinivas Pandruvada
2016-08-15 17:53 ` Dmitry Torokhov
2016-08-15 18:24 ` Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 6/7] hid: hid-sensor-hub: Add ISH quirk Srinivas Pandruvada
2016-08-07 9:25 ` [PATCH v4 7/7] MAINTAINERS: Add Intel ISH Srinivas Pandruvada
2016-08-07 17:03 ` [PATCH v4 0/7] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-08-17 9:17 ` 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=6ee7950c-8602-a4a1-b87c-0e6a60752c50@kernel.org \
--to=jic23@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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).