linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Daniel Baluta <daniel.baluta@intel.com>,
	linux-iio@vger.kernel.org, rafael.j.wysocki@intel.com
Subject: Re: [PATCH] iio kmx61 / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM
Date: Sat, 10 Jan 2015 09:30:14 -0800	[thread overview]
Message-ID: <20150110173014.GA7488@kroah.com> (raw)
In-Reply-To: <54B0FFDB.1020402@kernel.org>

On Sat, Jan 10, 2015 at 10:32:59AM +0000, Jonathan Cameron wrote:
> On 09/01/15 09:39, Daniel Baluta wrote:
> > After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
> > selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
> > depending on CONFIG_PM_RUNTIME may now be changed to depend on
> > CONFIG_PM.
> > 
> > Replace CONFIG_PM_RUNTIME with CONFIG_PM everywhere under
> > drivers/iio/imu/kmx61.c
> > 
> > Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
> Thanks Daniel, glad you tracked this down.  I was wondering why
> the autobuilders were happy but it broke for Greg! (short memory
> sometimes, given that patch was only a month ago).
> 
> Greg, as my tree is currently behind the point where Rafael did the big
> patch series to fix this (and hence doesn't have the precursor patch)
> there are two obvious solutions - either I rebase, or you take
> this one patch directly as a merge fix.
> 
> Which would you prefer?

I can take this one on top of your tree if you ack it, that sould solve
the issue.

thanks,

greg k-h

  reply	other threads:[~2015-01-10 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  9:39 [PATCH] iio kmx61 / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM Daniel Baluta
2015-01-10 10:32 ` Jonathan Cameron
2015-01-10 17:30   ` Greg KH [this message]
2015-01-15 21:01     ` Jonathan Cameron
2015-01-10 18:11 ` Jonathan Cameron

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=20150110173014.GA7488@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=rafael.j.wysocki@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).