From: Barry Song <21cnbao@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Qipan Li <Qipan.Li@csr.com>, Barry Song <Baohua.Song@csr.com>,
DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>
Subject: Re: [PATCH 2/3] serial: sirf: Use SIMPLE_DEV_PM_OPS macro
Date: Thu, 27 Feb 2014 20:04:58 +0800 [thread overview]
Message-ID: <CAGsJ_4y0LQuhM0M16Me99xSCtHCty_sNjtjwzZW6eQna9F0RRw@mail.gmail.com> (raw)
In-Reply-To: <001501cf33b1$5dfc0860$19f41920$%han@samsung.com>
2014-02-27 19:45 GMT+08:00 Jingoo Han <jg1.han@samsung.com>:
> Use SIMPLE_DEV_PM_OPS macro in order to make the code simpler.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
Acked-by: Barry Song <Baohua.Song@csr.com>
> drivers/tty/serial/sirfsoc_uart.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/sirfsoc_uart.c b/drivers/tty/serial/sirfsoc_uart.c
> index 68b0fd4..da96502 100644
> --- a/drivers/tty/serial/sirfsoc_uart.c
> +++ b/drivers/tty/serial/sirfsoc_uart.c
> @@ -1480,9 +1480,8 @@ static int sirfsoc_uart_resume(struct device *pdev)
> }
> #endif
>
> -static const struct dev_pm_ops sirfsoc_uart_pm_ops = {
> - SET_SYSTEM_SLEEP_PM_OPS(sirfsoc_uart_suspend, sirfsoc_uart_resume)
> -};
> +static SIMPLE_DEV_PM_OPS(sirfsoc_uart_pm_ops, sirfsoc_uart_suspend,
> + sirfsoc_uart_resume);
>
> static struct platform_driver sirfsoc_uart_driver = {
> .probe = sirfsoc_uart_probe,
> --
> 1.7.10.4
next prev parent reply other threads:[~2014-02-27 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 11:43 [PATCH 1/3] serial: st-asc: Use SIMPLE_DEV_PM_OPS macro Jingoo Han
2014-02-27 11:45 ` [PATCH 2/3] serial: sirf: " Jingoo Han
2014-02-27 12:04 ` Barry Song [this message]
2014-02-27 11:45 ` [PATCH 3/3] serial: tegra: " Jingoo Han
2014-02-27 16:44 ` Stephen Warren
2014-03-04 9:13 ` [PATCH 1/3] serial: st-asc: " srinivas kandagatla
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=CAGsJ_4y0LQuhM0M16Me99xSCtHCty_sNjtjwzZW6eQna9F0RRw@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=Qipan.Li@csr.com \
--cc=gregkh@linuxfoundation.org \
--cc=jg1.han@samsung.com \
--cc=linux-serial@vger.kernel.org \
--cc=workgroup.linux@csr.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;
as well as URLs for NNTP newsgroup(s).