stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Raj Sarraf <rrs@researchut.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Song Hongyan <hongyan.song@intel.com>,
	linux-iio <linux-iio@vger.kernel.org>
Cc: stable@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3
Date: Wed, 05 Apr 2017 16:21:59 +0530	[thread overview]
Message-ID: <1491389519.7588.1.camel@researchut.com> (raw)
In-Reply-To: <1491353080.3695.4.camel@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

On Tue, 2017-04-04 at 17:44 -0700, Srinivas Pandruvada wrote:
> Hi Ritesh,
> 
> Does the attached patch helps?

Thank you Srinivas. I tested your patch on top of 4.10.8 and it is working
perfect.

Ritesh

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-04-05 10:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1491035833.10386.1.camel@researchut.com>
     [not found] ` <1491059661.30396.37.camel@linux.intel.com>
2017-04-03 19:14   ` [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3 Ritesh Raj Sarraf
2017-04-05  0:44     ` Srinivas Pandruvada
2017-04-05  1:12       ` Song, Hongyan
2017-04-05 10:51       ` Ritesh Raj Sarraf [this message]
2017-04-05 15:35         ` Srinivas Pandruvada
2017-04-06  4:58           ` Song, Hongyan
2017-04-06  5:18             ` Srinivas Pandruvada
2017-04-05  4:59     ` Song, Hongyan

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=1491389519.7588.1.camel@researchut.com \
    --to=rrs@researchut.com \
    --cc=hongyan.song@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=stable@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).