public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Lee Jones <lee.jones@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] mfd: intel-lpss: save register context on suspend
Date: Fri, 15 Apr 2016 15:13:14 +0300	[thread overview]
Message-ID: <1460722394.6620.186.camel@linux.intel.com> (raw)
In-Reply-To: <20160330135439.GA20005@kuha.fi.intel.com>

On Wed, 2016-03-30 at 16:54 +0300, Heikki Krogerus wrote:
> Hi,
> 
> On Wed, Mar 30, 2016 at 04:35:46PM +0300, Andy Shevchenko wrote:
> > 
> > From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > 
> > All configurations are lost and the registers will have
> > default values when the hardware is suspended and resumed,
> > so saving the private register space context on suspend, and
> > restoring it on resume.
> > 
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > Acked-by: Lee Jones <lee.jones@linaro.org>
> Lee's Ack? I'm confused? Who is meant to take this patch?
> 
> > 
> > ---
> > Since v2:
> > - add Ack
> > - remove Fixes tag
> Why? This is a fix. And it also needs to go into the stable trees as
> well, so we will also need tag it with "Cc: stable@vger.kernel.org".

So, in that case v2 is what you want, right?

Lee, do I need to resend v2 as v4 or something else is required?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2016-04-15 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 13:35 [PATCH v3 1/1] mfd: intel-lpss: save register context on suspend Andy Shevchenko
2016-03-30 13:54 ` Heikki Krogerus
2016-04-15 12:13   ` Andy Shevchenko [this message]
2016-04-18  7:48     ` Lee Jones

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=1460722394.6620.186.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@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