From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Kevin Hilman <khilman@kernel.org>
Subject: Re: [PATCH] PM / Kconfig: Do not select PM directly from Kconfig files
Date: Mon, 01 Dec 2014 22:42:52 +0000 [thread overview]
Message-ID: <1709855.vJRHLWCgos@vostro.rjw.lan> (raw)
In-Reply-To: <CAMuHMdU-PH=L4L-Jt8BVCvcFwJJY6PhEEBPWtO3wLhh2ndyA6g@mail.gmail.com>
On Monday, December 01, 2014 10:21:54 AM Geert Uytterhoeven wrote:
> On Sat, Nov 29, 2014 at 2:03 AM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > It is not valid to select CONFIG_PM directly without selecting
> > CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME too, because that breaks
> > dependencies (ia64 does that) and it is not necessary to select
> > CONFIG_PM directly if CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME is
> > set, because it will be set automatically then (sh does that).
> >
> > Fix those mistakes.
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > ---
> > arch/ia64/Kconfig | 1 -
> > arch/sh/Kconfig | 1 -
>
> For the sh part:
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks!
> Note that sh is orphaned, so you should resend your patch to Andrew Morton,
> or queue it yourself.
Since it depends on material already in my tree, I'm going to queue it up myself.
Rafael
next prev parent reply other threads:[~2014-12-01 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 0:42 [PATCH] PM / Kconfig: Do not select PM directly from Kconfig files Rafael J. Wysocki
2014-12-01 9:21 ` Geert Uytterhoeven
2014-12-01 22:42 ` Rafael J. Wysocki [this message]
2014-12-02 1:10 ` Kevin Hilman
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=1709855.vJRHLWCgos@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=fenghua.yu@intel.com \
--cc=geert@linux-m68k.org \
--cc=khilman@kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=tony.luck@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