From: srinivas kandagatla <srinivas.kandagatla@st.com>
To: Jingoo Han <jg1.han@samsung.com>,
'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/3] serial: st-asc: Use SIMPLE_DEV_PM_OPS macro
Date: Tue, 4 Mar 2014 09:13:13 +0000 [thread overview]
Message-ID: <53159929.8020906@st.com> (raw)
In-Reply-To: <000f01cf33b1$32c234d0$98469e70$%han@samsung.com>
Thanks for the patch, It looks ok to me.
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@st.com>
On 27/02/14 11:43, Jingoo Han wrote:
> Use SIMPLE_DEV_PM_OPS macro in order to make the code simpler.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/tty/serial/st-asc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/st-asc.c b/drivers/tty/serial/st-asc.c
> index 21e6e84..93e27b9 100644
> --- a/drivers/tty/serial/st-asc.c
> +++ b/drivers/tty/serial/st-asc.c
> @@ -883,9 +883,8 @@ static struct uart_driver asc_uart_driver = {
> .cons = ASC_SERIAL_CONSOLE,
> };
>
> -static const struct dev_pm_ops asc_serial_pm_ops = {
> - SET_SYSTEM_SLEEP_PM_OPS(asc_serial_suspend, asc_serial_resume)
> -};
> +static SIMPLE_DEV_PM_OPS(asc_serial_pm_ops, asc_serial_suspend,
> + asc_serial_resume);
>
> static struct platform_driver asc_serial_driver = {
> .probe = asc_serial_probe,
>
prev parent reply other threads:[~2014-03-04 9:19 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
2014-02-27 11:45 ` [PATCH 3/3] serial: tegra: " Jingoo Han
2014-02-27 16:44 ` Stephen Warren
2014-03-04 9:13 ` srinivas kandagatla [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=53159929.8020906@st.com \
--to=srinivas.kandagatla@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=jg1.han@samsung.com \
--cc=linux-serial@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).