From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Chuanxiao.Dong" <chuanxiao.dong@intel.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
arjan.van.de.ven@intel.com
Subject: Re: [PATCH 1/1]nand/denali: Add runtime pm framework for MRST Denali NAND controller
Date: Mon, 30 Aug 2010 15:42:39 +0300 [thread overview]
Message-ID: <1283172159.12995.64.camel@brekeke> (raw)
In-Reply-To: <20100826081201.GA11565@intel.com>
Hi,
On Thu, 2010-08-26 at 16:12 +0800, Chuanxiao.Dong wrote:
> +static struct dev_pm_ops denali_pm = {
> + .runtime_suspend = denali_runtime_suspend,
> + .runtime_resume = denali_runtime_resume,
> + .runtime_idle = denali_runtime_idle,
> +};
> +#define DENALI_PM (&denali_pm)
I think it is confusing to use this style. Please, do not define this
DENALI_PM macro, unless this is a standard practice, which I doubt, but
not sure.
... snip ...
> +#else
> +#define DENALI_PM NULL
Ditto.
> +static inline void denali_timer_add(struct denali_nand_info *denali) {}
> +static inline void denali_timer_func(unsigned long ptr) {}
> +#endif
#endif /* !CONFIG_PM_RUNTIME */
.. snip ..
> static struct pci_driver denali_pci_driver = {
> + .driver = {
> + .pm = DENALI_PM,
> + },
This is the only place where you use this macro, just do
#ifdef CONFIG_PM_RUNTIME
.driver = {
.pm = DENALI_PM,
},
#endif
And it will be more readable.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-08-30 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 8:12 [PATCH 1/1]nand/denali: Add runtime pm framework for MRST Denali NAND controller Chuanxiao.Dong
2010-08-30 12:42 ` Artem Bityutskiy [this message]
2010-09-06 2:05 ` Dong, Chuanxiao
2010-09-06 5:39 ` Artem Bityutskiy
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=1283172159.12995.64.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=arjan.van.de.ven@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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).