From: Peng Ma <peng.ma@nxp.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: "a.zummo@towertech.it" <a.zummo@towertech.it>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>, Ran Wang <ran.wang_1@nxp.com>,
Biwen Li <biwen.li@nxp.com>
Subject: RE: [EXT] Re: [PATCH] rtc: fsl-ftm-alarm: enable acpi support
Date: Mon, 23 Mar 2020 00:53:54 +0000 [thread overview]
Message-ID: <AM7PR04MB7016DC4509F3493856641EB1EDF00@AM7PR04MB7016.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200322211237.GD221863@piout.net>
Hi Alexandre,
OK, Got it.
Thanks very much.
Best Regards,
Peng
>-----Original Message-----
>From: Alexandre Belloni <alexandre.belloni@bootlin.com>
>Sent: 2020年3月23日 5:13
>To: Peng Ma <peng.ma@nxp.com>
>Cc: a.zummo@towertech.it; linux-rtc@vger.kernel.org;
>linux-kernel@vger.kernel.org; Leo Li <leoyang.li@nxp.com>; Ran Wang
><ran.wang_1@nxp.com>; Biwen Li <biwen.li@nxp.com>
>Subject: [EXT] Re: [PATCH] rtc: fsl-ftm-alarm: enable acpi support
>
>Caution: EXT Email
>
>On 18/03/2020 10:53:54+0800, Peng Ma wrote:
>> This patch enables ACPI support in Rtc Flex timer driver.
>>
>> Signed-off-by: Peng Ma <peng.ma@nxp.com>
>> ---
>> drivers/rtc/rtc-fsl-ftm-alarm.c | 20 +++++++++++++++-----
>> 1 file changed, 15 insertions(+), 5 deletions(-)
>>
>Applied, thanks.
>
>--
>Alexandre Belloni, Bootlin
>Embedded Linux and Kernel engineering
>https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.c
>om&data=02%7C01%7Cpeng.ma%40nxp.com%7Cde862f8556e5440c9dcf0
>8d7cea5c0b3%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6372050
>83604609156&sdata=cN%2BVcgd1GZcqKt3Qx7T6v3%2Fq%2FwPXIZPyUDx9
>vtoYdtI%3D&reserved=0
prev parent reply other threads:[~2020-03-23 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 2:53 [PATCH] rtc: fsl-ftm-alarm: enable acpi support Peng Ma
2020-03-22 21:12 ` Alexandre Belloni
2020-03-23 0:53 ` Peng Ma [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=AM7PR04MB7016DC4509F3493856641EB1EDF00@AM7PR04MB7016.eurprd04.prod.outlook.com \
--to=peng.ma@nxp.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=biwen.li@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=ran.wang_1@nxp.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).