From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>, hongyan.song@intel.com
Cc: linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
hdegoede@redhat.com, jic23@kernel.org, even.xu@intel.com
Subject: Re: [PATCH v3] hid: remove NO_D3 flag when remove driver
Date: Wed, 26 Jun 2019 08:30:01 -0700 [thread overview]
Message-ID: <67a1ec6dd44866c29333f5b05184cc402bc20382.camel@linux.intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1906261406120.27227@cbobk.fhfr.pm>
On Wed, 2019-06-26 at 14:07 +0200, Jiri Kosina wrote:
> On Sun, 2 Jun 2019, hongyan.song@intel.com wrote:
>
> > From: Song Hongyan <hongyan.song@intel.com>
> >
> > Remove the NO_D3 flag when remove the driver and let device enter
> > into D3, it will save more power.
> >
> > Signed-off-by: Song Hongyan <hongyan.song@intel.com>
> > Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> > ---
> > v3 changes:
> > After test the former implmentation, we found FW will enter D3 when
> > system enter into S0i3. Change the implementation to meet the
> > requirement:
> > device enter D3 and have no impact to ISH platform.
>
> Srinivas, I'd prefer changes like this to go to Linus tree in merge
> window
> and not -rc phase, so I'll do that unless you tell me there is a
> good
> reason to push it to Linus still in -rc.
Correct. I will tell you if it is important enough to go to -rc
release, otherwise all changes you can assume for the next merge
window.
This change is also for the next merge window.
Thanks,
Srinivas
>
> Thanks,
>
next prev parent reply other threads:[~2019-06-26 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 0:17 [PATCH v3] hid: remove NO_D3 flag when remove driver hongyan.song
2019-06-26 12:07 ` Jiri Kosina
2019-06-26 15:30 ` Srinivas Pandruvada [this message]
2019-06-26 21:35 ` Jiri Kosina
2019-06-27 0:43 ` 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=67a1ec6dd44866c29333f5b05184cc402bc20382.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.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