From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Sean Wang <sean.wang@mediatek.com>
Cc: Yingjoe Chen <yingjoe.chen@mediatek.com>,
a.zummo@towertech.it, robh+dt@kernel.org, mark.rutland@arm.com,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] rtc: mediatek: add driver for RTC on MT7622 SoC
Date: Thu, 19 Oct 2017 12:13:49 +0200 [thread overview]
Message-ID: <20171019101349.bo3wwj7mdfdmkdxs@piout.net> (raw)
In-Reply-To: <1508407479.29850.5.camel@mtkswgap22>
On 19/10/2017 at 18:04:39 +0800, Sean Wang wrote:
> I prefer to 2001 to 2099 only which can be completely handled in the
> common logic. Extra specific logic simply for 2100 seems not be
> worthwhile.
>
Agreed.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-19 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 9:40 [PATCH v2 0/4] rtc: mediatek: add support for SoC based RTC on MT7622 sean.wang
2017-10-17 9:40 ` [PATCH v2 1/4] dt-bindings: rtc: mediatek: add bindings for MediaTek SoC based RTC sean.wang
2017-10-18 13:32 ` Yingjoe Chen
2017-10-19 3:00 ` Sean Wang
2017-10-17 9:40 ` [PATCH v2 2/4] rtc: mediatek: add driver for RTC on MT7622 SoC sean.wang
2017-10-18 9:52 ` Yingjoe Chen
2017-10-19 2:18 ` Sean Wang
2017-10-18 11:12 ` Yingjoe Chen
2017-10-18 12:57 ` Alexandre Belloni
2017-10-19 2:55 ` Sean Wang
2017-10-19 9:02 ` Alexandre Belloni
2017-10-19 10:04 ` Sean Wang
2017-10-19 10:13 ` Alexandre Belloni [this message]
2017-10-17 9:40 ` [PATCH v2 3/4] rtc: mediatek: enhance the description for MediaTek PMIC based RTC sean.wang
2017-10-17 9:40 ` [PATCH v2 4/4] rtc: mediatek: update MAINTAINERS entry with MediaTek RTC driver sean.wang
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=20171019101349.bo3wwj7mdfdmkdxs@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=yingjoe.chen@mediatek.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
all inboxes | Powered by JetHome®