From: Tony Lindgren <tony@atomide.com>
To: Omar Ramirez Luna <omar.luna@linaro.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Ohad Ben-Cohen <ohad@wizery.com>,
Suman Anna <s-anna@ti.com>, Juan Gutierrez <jgutierrez@ti.com>,
Felipe Contreras <felipe.contreras@nokia.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org
Subject: Re: [PATCH 1/2] ARM: OMAP2+: move mailbox.h out of plat-omap headers
Date: Mon, 29 Oct 2012 10:52:28 -0700 [thread overview]
Message-ID: <20121029175228.GD11908@atomide.com> (raw)
In-Reply-To: <1351530381-11459-2-git-send-email-omar.luna@linaro.org>
Hi,
> --- /dev/null
> +++ b/include/linux/platform_data/omap_mailbox.h
> @@ -0,0 +1,105 @@
This file should only contain pure platform data needed
by the core omap code to pass to the mailbox driver.
The mailbox API header should be somewhere else,
like include/linux/mailbox/mailbox-omap.h or similar.
But shouldn't this all now be handled by using the
remoteproc framework?
Regards,
Tony
next prev parent reply other threads:[~2012-10-29 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 17:06 [PATCH 0/2] ARM: OMAP: mailbox out of plat code Omar Ramirez Luna
2012-10-29 17:06 ` [PATCH 1/2] ARM: OMAP2+: move mailbox.h out of plat-omap headers Omar Ramirez Luna
2012-10-29 17:52 ` Tony Lindgren [this message]
2012-10-30 12:18 ` Omar Ramirez Luna
2012-10-30 16:24 ` Tony Lindgren
2012-10-30 21:02 ` Greg Kroah-Hartman
2012-10-31 7:22 ` Omar Ramirez Luna
2012-10-31 8:45 ` Loic PALLARDY
2012-10-31 18:24 ` Tony Lindgren
2012-10-29 17:06 ` [PATCH 2/2] mailbox: OMAP: introduce mailbox framework Omar Ramirez Luna
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=20121029175228.GD11908@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@nokia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgutierrez@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=omar.luna@linaro.org \
--cc=s-anna@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).