From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: tps65090: Fix ifdefs for suspend mode
Date: Mon, 26 Mar 2012 12:00:40 +0100 [thread overview]
Message-ID: <20120326110039.GK3098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6DD312816E@BGMAIL02.nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Mon, Mar 26, 2012 at 09:21:33AM +0530, Venu Byravarasu wrote:
> > CONFIG_PM also covers runtime only PM.
> As CONFIG_PM covers both runtime and full system suspend/resume
> activities, I do not really understand what we gain with this change.
> Can you please provide more details?
You've only got system sleep PM operations, CONFIG_PM will leave them
built when CONFIG_PM_SLEEP is disabled so you'll get build warnings.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-26 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 18:39 [PATCH 1/2] mfd: tps65090: Fix ifdefs for suspend mode Mark Brown
2012-03-22 18:39 ` [PATCH 2/2] mfd: tps65090: Don't use I2C-specific suspend and resume operations Mark Brown
2012-03-26 3:45 ` Venu Byravarasu
2012-03-26 10:59 ` Mark Brown
2012-03-26 11:00 ` Venu Byravarasu
2012-03-26 11:04 ` Venu Byravarasu
2012-03-26 3:51 ` [PATCH 1/2] mfd: tps65090: Fix ifdefs for suspend mode Venu Byravarasu
2012-03-26 11:00 ` Mark Brown [this message]
2012-03-26 11:04 ` Venu Byravarasu
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=20120326110039.GK3098@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=vbyravarasu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.