From: David Miller <davem@davemloft.net>
To: cooldavid@cooldavid.org
Cc: netdev@vger.kernel.org, arieslee@jmicron.com, devinchiu@jmicron.com
Subject: Re: [PATCH net-next-2.6 1/2] jme: Fix compile warning introduced by new pm macro
Date: Thu, 30 Jun 2011 23:54:57 -0700 (PDT) [thread overview]
Message-ID: <20110630.235457.469685964871620732.davem@davemloft.net> (raw)
In-Reply-To: <1309238615-25590-1-git-send-email-cooldavid@cooldavid.org>
From: "Guo-Fu Tseng" <cooldavid@cooldavid.org>
Date: Tue, 28 Jun 2011 13:23:34 +0800
> From: Guo-Fu Tseng <cooldavid@cooldavid.org>
>
> SIMPLE_DEV_PM_OPS is using SET_SYSTEM_SLEEP_PM_OPS
> and SET_SYSTEM_SLEEP_PM_OPS is empty when CONFIG_PM_SLEEP
> is not defined.
>
> Switching #ifdef CONFIG_PM to #ifdef CONFIG_PM_SLEEP
>
> Signed-off-by: Guo-Fu Tseng <cooldavid@cooldavid.org>
Applied
prev parent reply other threads:[~2011-07-01 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 5:23 [PATCH net-next-2.6 1/2] jme: Fix compile warning introduced by new pm macro Guo-Fu Tseng
2011-06-28 5:23 ` [PATCH net-next-2.6 2/2] jme: Cleanup PM operations after using new PM API Guo-Fu Tseng
2011-06-28 11:19 ` Guo-Fu Tseng
2011-07-01 6:54 ` David Miller [this message]
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=20110630.235457.469685964871620732.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arieslee@jmicron.com \
--cc=cooldavid@cooldavid.org \
--cc=devinchiu@jmicron.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).