From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Cc: Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>,
Benoit Cousson <bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] hwspinlock/omap: add support for dt nodes
Date: Thu, 3 Oct 2013 11:19:09 -0700 [thread overview]
Message-ID: <20131003181909.GT8949@atomide.com> (raw)
In-Reply-To: <524DB48B.7020906-l0cyMroinI0@public.gmane.org>
* Suman Anna <s-anna-l0cyMroinI0@public.gmane.org> [131003 11:25]:
> Tony,
>
> On 10/03/2013 01:05 PM, Tony Lindgren wrote:
> > * Suman Anna <s-anna-l0cyMroinI0@public.gmane.org> [130903 11:00]:
> >> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> >> which are all device-tree boot only. This patch adds the
> >> base support for parsing the DT nodes, and removes the code
> >> dealing with the traditional platform device instantiation.
> >
> > Great, this should be safe for Ohad to queue:
> >
> > Acked-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
> >
>
> There is a v2 of this series [1] that adds additional SoC support as
> well. It currently has some comments [2] & [3] from Mark Rutland on the
> DT bindings. I am looking into that at the moment and it may change this
> patch as well (the DT parse portion of it in
> drivers/hwspinlock/omap_hwspinlock).
OK, yeah I noticed there's some pending comments. Feel free to keep my
ack for the arch/arm/mach-omap2 removal parts, those won't likely
change.
Regards,
Tony
> [1] http://marc.info/?l=linux-omap&m=137944644112727&w=2
> [2] http://marc.info/?t=137944636400005&r=1&w=2
> [3] http://marc.info/?t=137944636400004&r=1&w=2
>
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Benoit Cousson <bcousson@baylibre.com>,
Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] hwspinlock/omap: add support for dt nodes
Date: Thu, 3 Oct 2013 11:19:09 -0700 [thread overview]
Message-ID: <20131003181909.GT8949@atomide.com> (raw)
In-Reply-To: <524DB48B.7020906@ti.com>
* Suman Anna <s-anna@ti.com> [131003 11:25]:
> Tony,
>
> On 10/03/2013 01:05 PM, Tony Lindgren wrote:
> > * Suman Anna <s-anna@ti.com> [130903 11:00]:
> >> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> >> which are all device-tree boot only. This patch adds the
> >> base support for parsing the DT nodes, and removes the code
> >> dealing with the traditional platform device instantiation.
> >
> > Great, this should be safe for Ohad to queue:
> >
> > Acked-by: Tony Lindgren <tony@atomide.com>
> >
>
> There is a v2 of this series [1] that adds additional SoC support as
> well. It currently has some comments [2] & [3] from Mark Rutland on the
> DT bindings. I am looking into that at the moment and it may change this
> patch as well (the DT parse portion of it in
> drivers/hwspinlock/omap_hwspinlock).
OK, yeah I noticed there's some pending comments. Feel free to keep my
ack for the arch/arm/mach-omap2 removal parts, those won't likely
change.
Regards,
Tony
> [1] http://marc.info/?l=linux-omap&m=137944644112727&w=2
> [2] http://marc.info/?t=137944636400005&r=1&w=2
> [3] http://marc.info/?t=137944636400004&r=1&w=2
>
>
next prev parent reply other threads:[~2013-10-03 18:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 17:52 [PATCH 1/2] hwspinlock/omap: add support for dt nodes Suman Anna
2013-09-03 17:52 ` Suman Anna
2013-09-03 18:50 ` Kumar Gala
2013-09-03 18:50 ` Kumar Gala
2013-09-03 19:10 ` Suman Anna
2013-09-03 19:10 ` Suman Anna
2013-09-03 19:37 ` Kumar Gala
2013-09-03 19:37 ` Kumar Gala
2013-09-03 22:34 ` Suman Anna
2013-09-03 22:34 ` Suman Anna
2013-09-04 14:46 ` Kumar Gala
2013-09-04 14:46 ` Kumar Gala
2013-09-04 16:27 ` Suman Anna
2013-09-04 16:27 ` Suman Anna
2013-09-04 16:42 ` Kumar Gala
2013-09-04 16:42 ` Kumar Gala
2013-09-04 17:03 ` Suman Anna
2013-09-04 17:03 ` Suman Anna
2013-09-04 17:51 ` Kumar Gala
2013-09-04 17:51 ` Kumar Gala
2013-09-04 20:04 ` Suman Anna
2013-09-04 20:04 ` Suman Anna
2013-09-04 8:09 ` Stanimir Varbanov
2013-09-04 16:30 ` Suman Anna
2013-09-04 16:30 ` Suman Anna
2013-10-03 18:05 ` Tony Lindgren
[not found] ` <20131003180546.GP8949-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-10-03 18:16 ` Suman Anna
2013-10-03 18:16 ` Suman Anna
[not found] ` <524DB48B.7020906-l0cyMroinI0@public.gmane.org>
2013-10-03 18:19 ` Tony Lindgren [this message]
2013-10-03 18:19 ` Tony Lindgren
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=20131003181909.GT8949@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
--cc=s-anna-l0cyMroinI0@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.