From: Philipp Zabel <p.zabel@pengutronix.de>
To: Suman Anna <s-anna@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Andrew F. Davis" <afd@ti.com>, Tero Kristo <t-kristo@ti.com>,
Nishanth Menon <nm@ti.com>, Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCH v5 0/2] Add TI SCI Reset Driver
Date: Tue, 06 Jun 2017 09:51:11 +0200 [thread overview]
Message-ID: <1496735471.2966.4.camel@pengutronix.de> (raw)
In-Reply-To: <04a25503-b675-8832-0323-eb7ecbaaefeb@ti.com>
Hi Suman,
On Fri, 2017-06-02 at 11:45 -0500, Suman Anna wrote:
[...]
> > [1] http://marc.info/?l=devicetree&m=147976458332492&w=2
> > [2] http://marc.info/?l=linux-arm-kernel&m=149547831708124&w=2
> > [3] https://patchwork.kernel.org/patch/9744909/
> >
> > Andrew F. Davis (2):
> > Documentation: dt: reset: Add TI SCI reset binding
> > reset: Add the TI SCI reset driver
> >
>
> Can you pick up this series for v4.13 if there are no comments. Btw, [2]
> is acked by Rob. Will appreciate if you can fixup the patch header from
> "Documentation: dt: reset: ..." to "dt-bindings: reset: ..." on the
> first patch when applying. Thanks in advance.
Thank you for the reminder, I've now applied both to the reset/next
branch. I've fixed the dt-bindings patch commit message as you suggested
and made the struct reset_control_ops const in the driver patch.
regards
Philipp
prev parent reply other threads:[~2017-06-06 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 18:09 [PATCH v5 0/2] Add TI SCI Reset Driver Suman Anna
2017-05-24 18:09 ` [PATCH v5 1/2] Documentation: dt: reset: Add TI SCI reset binding Suman Anna
2017-05-24 18:09 ` [PATCH v5 2/2] reset: Add the TI SCI reset driver Suman Anna
2017-06-02 16:45 ` [PATCH v5 0/2] Add TI SCI Reset Driver Suman Anna
2017-06-06 7:51 ` Philipp Zabel [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=1496735471.2966.4.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=afd@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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).