linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "jikos@kernel.org" <jikos@kernel.org>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>,
	"Song, Hongyan" <hongyan.song@intel.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"Xu, Even" <even.xu@intel.com>
Subject: Re: [PATCH] hid: remove NO_D3 flag for ish not CHV platform
Date: Wed, 29 May 2019 03:27:46 +0000	[thread overview]
Message-ID: <db5a3a3828c8be89b52ebfe4ebf5b863a8d87f03.camel@intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1905241109390.1962@cbobk.fhfr.pm>

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

On Fri, 2019-05-24 at 11:10 +0200, Jiri Kosina wrote:
> On Wed, 22 May 2019, Pandruvada, Srinivas wrote:
> 
> > > > From: Song Hongyan <hongyan.song@intel.com>
> > 
> > Also commit summary "hid: remove NO_D3 flag for non Cherry Trail
> > (CHT)"
> > 
> > > > 
> > > > NO_D3 flag is set for CHV and the older platforms, the other
> > > > platform
> > > > suppose can enter D3, if have this NO_D3 flag set it can never
> > > > enter D3
> > > 
> > > Could you please provide a little bit more descriptive changelog
> > > --
> > > namely 
> > > what observable problem is it fixing.
> > 
> > 
> > In addition, I don't think this is a rc2+ release fix.
> 
> Thanks Srinivas. Could you please Ack v2 so that I could queue it?
I want some more information in the commit and test information. So
Song will submit v3.

Thanks,
Srinivas


> 

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3290 bytes --]

      reply	other threads:[~2019-05-29  3:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17  8:46 [PATCH] hid: remove NO_D3 flag for ish not CHV platform hongyan.song
2019-05-22 10:36 ` Jiri Kosina
2019-05-22 18:04   ` Pandruvada, Srinivas
2019-05-24  9:10     ` Jiri Kosina
2019-05-29  3:27       ` Pandruvada, Srinivas [this message]

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=db5a3a3828c8be89b52ebfe4ebf5b863a8d87f03.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=even.xu@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=hongyan.song@intel.com \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@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).