From: Jason Cooper <jason@lakedaemon.net>
To: Matti Vaittinen <matti.vaittinen@nsn.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
"linux@roeck-us.net" <linux@roeck-us.net>,
a.zummo@towertech.it, "jic23@kernel.org" <jic23@kernel.org>,
"arno@natisbad.org" <arno@natisbad.org>,
jgunthorpe@obsidianresearch.com, san@rosetechnology.dk,
hs@denx.de,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Sverdlin Alexander <alexander.sverdlin@nsn.com>
Subject: Re: [RESEND PATCH v3] rtc: ds1307: add trickle charger device tree binding
Date: Tue, 9 Sep 2014 07:27:50 -0400 [thread overview]
Message-ID: <20140909112750.GK30828@titan.lakedaemon.net> (raw)
In-Reply-To: <20140909082902.GD21342@fi-ourus-dhcp00977.emea.nsn-net.net>
On Tue, Sep 09, 2014 at 11:29:11AM +0300, Matti Vaittinen wrote:
> On Mon, Sep 08, 2014 at 07:26:57AM -0400, ext Jason Cooper wrote:
> > Matti,
> >
> > On Mon, Sep 08, 2014 at 10:32:24AM +0300, Matti Vaittinen wrote:
> > > ---
> >
> > Here. Otherwise, it'll get included in the commit message, which I
> > don't think was your intention.
>
> Ok, thanks.
>
> >
> > > .../devicetree/bindings/i2c/trivial-devices.txt | 1 -
> > > .../devicetree/bindings/rtc/dallas,ds1339.txt | 18 ++++++
> > > drivers/rtc/rtc-ds1307.c | 66 ++++++++++++++++++++--
> > > 3 files changed, 80 insertions(+), 5 deletions(-)
> > > create mode 100644 Documentation/devicetree/bindings/rtc/dallas,ds1339.txt
> >
> > I would split this into two patches, one for the binding documentation,
> > and one for the C file changes. You can then use
> > ./scripts/get_maintainer.pl to see who the rtc maintainer is (nothing
> > jumps out from my memory).
>
> Splitting sounds reasonable. I will do this and also invert the default
> diode setting to be connected as was suggested by Pavel in mail responce
> to v1 of patch. And Alessandro is the maintainer for rtc according to
> the MAINTAINERS file.
>
> >
> > Most likely, the rtc maintainer will take the series with the DT
> > maintainers Acks. You made all the binding changes as discussed by Mark
> > and I, so fwiw,
> >
> > Acked-by: Jason Cooper <jason@lakedaemon.net>
> >
> > Just keep in mind that I'm not a DT maintainer, I've just moved a lot of
> > patches into that area :-P When you respin the series to split it, just
> > throw my Ack on the binding docs.
>
> Thanks, although the doc will change when I invert the default diode
> setting =)
Yep, I'm fine with the inversion. Feel free to keep the Ack.
thx,
Jason.
prev parent reply other threads:[~2014-09-09 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 7:32 Matti Vaittinen
2014-09-08 11:26 ` Jason Cooper
2014-09-08 11:29 ` Alessandro Zummo
2014-09-09 8:29 ` Matti Vaittinen
2014-09-09 11:27 ` Jason Cooper [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=20140909112750.GK30828@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=a.zummo@towertech.it \
--cc=alexander.sverdlin@nsn.com \
--cc=arno@natisbad.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hs@denx.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@nsn.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=san@rosetechnology.dk \
/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®