All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, "'Len Brown'" <len.brown@intel.com>,
	"'Pavel Machek'" <pavel@ucw.cz>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] PM: Add pm_ops_ptr() macro
Date: Sat, 27 Apr 2013 16:40:36 +0200	[thread overview]
Message-ID: <20119404.Sfu5WntByi@vostro.rjw.lan> (raw)
In-Reply-To: <000001ce42f2$96128cc0$c237a640$@samsung.com>

On Saturday, April 27, 2013 11:54:50 AM Jingoo Han wrote:
> Add pm_ops_ptr() macro that allows the .pm entry in the driver structures
> to be assigned without having an #define xxx NULL for the case that PM is
> not enabled.
> 
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>

First, I'm not taking any more PM patches for v3.10 (that don't fix recent
regressions).

Second, please add that macro along with a user.

Thanks,
Rafael


> ---
>  include/linux/pm.h |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index a224c7f..bd50d15 100644
> --- a/include/linux/pm.h
> +++ b/include/linux/pm.h
> @@ -55,8 +55,10 @@ struct device;
>  
>  #ifdef CONFIG_PM
>  extern const char power_group_name[];		/* = "power" */
> +#define pm_ops_ptr(_ptr)	(_ptr)
>  #else
>  #define power_group_name	NULL
> +#define pm_ops_ptr(_ptr)	NULL
>  #endif
>  
>  typedef struct pm_message {
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-04-27 14:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27  2:54 [PATCH] PM: Add pm_ops_ptr() macro Jingoo Han
2013-04-27 14:40 ` Rafael J. Wysocki [this message]
2013-04-29  5:41   ` Jingoo Han
2013-04-29 11:35     ` Rafael J. Wysocki
2013-04-30  0:21       ` Jingoo Han
2013-04-29 12:12     ` Lars-Peter Clausen
2013-04-30  0:54       ` Jingoo Han
2013-04-30  1:09 Jingoo Han
2013-04-30  1:09 ` Jingoo Han
2013-05-02 21:18 ` Rafael J. Wysocki
2013-05-02 21:18   ` Rafael J. Wysocki
2013-05-03  9:23   ` Pavel Machek
2013-05-30 10:56     ` Wolfram Sang
2013-05-30 10:56       ` Wolfram Sang
2013-05-30 13:54       ` Rafael J. Wysocki
2013-05-30 13:54         ` Rafael J. Wysocki

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=20119404.Sfu5WntByi@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=jg1.han@samsung.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.