From: Sean Wang <sean.wang@mediatek.com>
To: Yingjoe Chen <yingjoe.chen@mediatek.com>
Cc: a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
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 1/4] dt-bindings: rtc: mediatek: add bindings for MediaTek SoC based RTC
Date: Thu, 19 Oct 2017 11:00:18 +0800 [thread overview]
Message-ID: <1508382018.21840.124.camel@mtkswgap22> (raw)
In-Reply-To: <1508333529.13340.26.camel@mtksdaap41>
On Wed, 2017-10-18 at 21:32 +0800, Yingjoe Chen wrote:
> On Tue, 2017-10-17 at 17:40 +0800, sean.wang@mediatek.com wrote:
> > From: Sean Wang <sean.wang@mediatek.com>
> >
> > Add device-tree binding for MediaTek SoC based RTC
> >
> > Cc: devicetree@vger.kernel.org
> > Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> > .../devicetree/bindings/rtc/rtc-mediatek.txt | 21 +++++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mediatek.txt
> >
> > diff --git a/Documentation/devicetree/bindings/rtc/rtc-mediatek.txt b/Documentation/devicetree/bindings/rtc/rtc-mediatek.txt
> > new file mode 100644
> > index 0000000..09fe8f5
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/rtc/rtc-mediatek.txt
>
>
> How about change this filename to match driver filename change?
>
> Joe.C
>
Will be improved together with the other patches
next prev parent reply other threads:[~2017-10-19 3:00 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-NuS5LvNUpcJWk0Htik3J/w
2017-10-17 9:40 ` [PATCH v2 1/4] dt-bindings: rtc: mediatek: add bindings for MediaTek SoC based RTC sean.wang
[not found] ` <235e4bdaa605021facf4ab5c4e8a2ecc5293516d.1508231935.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-10-18 13:32 ` Yingjoe Chen
2017-10-19 3:00 ` Sean Wang [this message]
[not found] ` <cover.1508231935.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-10-17 9:40 ` [PATCH v2 2/4] rtc: mediatek: add driver for RTC on MT7622 SoC sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-10-18 9:52 ` Yingjoe Chen
2017-10-19 2:18 ` Sean Wang
[not found] ` <2f86eebfd380cf932808df3404e2f4a6f2f0f874.1508231935.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-10-18 11:12 ` Yingjoe Chen
2017-10-18 12:57 ` Alexandre Belloni
[not found] ` <20171018125743.kqna6b4lgng674om-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2017-10-19 2:55 ` Sean Wang
2017-10-19 9:02 ` Alexandre Belloni
[not found] ` <20171019090219.2odtq3xosqk5ytsb-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2017-10-19 10:04 ` Sean Wang
2017-10-19 10:13 ` Alexandre Belloni
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=1508382018.21840.124.camel@mtkswgap22 \
--to=sean.wang@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--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=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;
as well as URLs for NNTP newsgroup(s).