devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Ramirez Luna <omar.luna@linaro.org>
To: Benoit Cousson <b-cousson@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>,
	Russell King <linux@arm.linux.org.uk>,
	Vaibhav Bedia <vaibhav.bedia@ti.com>,
	Omar Ramirez Luna <omar.luna@linaro.org>,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, patches@linaro.org,
	linaro-dev@lists.linaro.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 0/2] OMAP: mailbox initial device tree support
Date: Wed, 23 May 2012 17:03:51 -0500	[thread overview]
Message-ID: <CALLhW=7ENCpodLxf-vaY6EzYRv9uKz_52FDsUbMAaSGNFy4LiQ@mail.gmail.com> (raw)
In-Reply-To: <1335894460-19941-1-git-send-email-omar.luna@linaro.org>

Hi Tony, Benoit,

On 1 May 2012 12:47, Omar Ramirez Luna <omar.luna@linaro.org> wrote:
> To allow mailbox driver to function with device tree.
>
> Tested in OMAP4 and OMAP3. OMAP2 untested.
>
> Omar Ramirez Luna (2):
>  OMAP: mailbox: add device tree support
>  arm/dts: OMAP2+: Add mailbox nodes
>
>  .../devicetree/bindings/arm/omap/mailbox.txt       |    9 +++++++++
>  arch/arm/boot/dts/omap2.dtsi                       |    5 +++++
>  arch/arm/boot/dts/omap3.dtsi                       |    5 +++++
>  arch/arm/boot/dts/omap4.dtsi                       |    5 +++++
>  arch/arm/mach-omap2/devices.c                      |    3 +++
>  arch/arm/mach-omap2/mailbox.c                      |   12 ++++++++++++
>  6 files changed, 39 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/omap/mailbox.txt

Can you share your thoughts for these patches?

Regards,

Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2012-05-23 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 17:47 [PATCH 0/2] OMAP: mailbox initial device tree support Omar Ramirez Luna
2012-05-01 17:47 ` [PATCH 1/2] OMAP: mailbox: add " Omar Ramirez Luna
2012-05-01 17:47 ` [PATCH 2/2] arm/dts: OMAP2+: Add mailbox nodes Omar Ramirez Luna
2012-05-24 15:47   ` Cousson, Benoit
2012-05-02  5:42 ` [PATCH 0/2] OMAP: mailbox initial device tree support Bedia, Vaibhav
     [not found]   ` <B5906170F1614E41A8A28DE3B8D121433EA68F6D-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-05-09 23:48     ` Omar Ramirez Luna
2012-05-24 15:44   ` Cousson, Benoit
     [not found]     ` <4FBE574F.6070408-l0cyMroinI0@public.gmane.org>
2012-05-30 19:31       ` Omar Ramirez Luna
2012-05-23 22:03 ` Omar Ramirez Luna [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='CALLhW=7ENCpodLxf-vaY6EzYRv9uKz_52FDsUbMAaSGNFy4LiQ@mail.gmail.com' \
    --to=omar.luna@linaro.org \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=patches@linaro.org \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=tony@atomide.com \
    --cc=vaibhav.bedia@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).