From: Mark Rutland <mark.rutland@arm.com>
To: "Anna, Suman" <s-anna@ti.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Tony Lindgren <tony@atomide.com>,
Benoit Cousson <bcousson@baylibre.com>,
Kumar Gala <galak@codeaurora.org>, Paul Walmsley <paul@pwsan.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCHv3 0/8] omap hwspinlock dt support
Date: Wed, 13 Nov 2013 09:36:22 +0000 [thread overview]
Message-ID: <20131113093622.GA21713@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <5282708A.30601@ti.com>
On Tue, Nov 12, 2013 at 06:16:42PM +0000, Anna, Suman wrote:
>
> > Hi,
> >
> > This is an updated series addressing the review comments from the
> > v2 series. The hwmod patches have been dropped from the repost
> > as per Paul's request, they have already been queued.
>
> Mark,
Hi Suman,
>
> Any comments on this series? Tony has picked up the OMAP DTS patches for
> 3.13, and so
> the "ti,omap4-hwspinlock" compatible string is showing up as
> undocumented in linux-next.
> How do you want me to proceed here? I will be separating out the
> bindings into separate patches
> in the future.
The only thing I note that I'm not so keen on is that the
hwlock-specifier is always one cell, rather than using a #hwlock-cells
property on the provider (even if we required it to be <1> for the
moment and just failed if it wasn't).
If possible, I would like an amendment to always use #hwlock-cells, but
otherwise this looks fine to me. Feel free to add my Ack:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
prev parent reply other threads:[~2013-11-13 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 21:15 Suman Anna
2013-10-10 21:15 ` [PATCHv3 1/8] hwspinlock/core: maintain a list of registered hwspinlock banks Suman Anna
2013-10-10 21:15 ` [PATCHv3 2/8] hwspinlock/core: add common dt bindings and OF helpers Suman Anna
2013-10-10 21:15 ` [PATCHv3 3/8] hwspinlock/omap: add support for dt nodes Suman Anna
2013-10-10 21:15 ` [PATCHv3 4/8] hwspinlock/omap: enable module before reading SYSSTATUS register Suman Anna
2013-10-10 21:15 ` [PATCHv3 5/8] hwspinlock/omap: support AM33xx Suman Anna
2013-10-10 21:15 ` [PATCHv3 6/8] ARM: dts: OMAP4: Add hwspinlock node Suman Anna
2013-10-11 23:41 ` Tony Lindgren
2013-10-29 20:59 ` Tony Lindgren
2013-10-10 21:15 ` [PATCHv3 7/8] ARM: dts: OMAP5: " Suman Anna
2013-10-10 21:15 ` [PATCHv3 8/8] ARM: dts: AM33XX: " Suman Anna
2013-11-12 18:16 ` [PATCHv3 0/8] omap hwspinlock dt support Anna, Suman
2013-11-13 9:36 ` Mark Rutland [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=20131113093622.GA21713@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=paul@pwsan.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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®