From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h>
Date: Fri, 28 Sep 2012 08:13:13 -0700 [thread overview]
Message-ID: <20120928151051.GC4840@atomide.com> (raw)
In-Reply-To: <1348815748-30072-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [120928 00:08]:
> In order to make single zImage work for ARM architecture,
> we need to make sure we don't depend on private headers.
>
> Move USB platform_data to <linux/platform_data/omap-usb.h>
The new standard seems to be subsystem-soc.h, so usb-omap.h :)
> and keep only internal functions in <plat/usb.h>.
Can the remaining parts be in #include "usb.h" in mach-omap2?
Regards,
Tony
next prev parent reply other threads:[~2012-09-28 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120927202615.GS4840@atomide.com>
2012-09-28 7:02 ` [PATCH] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h> Felipe Balbi
2012-09-28 15:13 ` Tony Lindgren [this message]
[not found] <20121016230040.GP15569@atomide.com>
2012-10-17 15:43 ` Felipe Balbi
2012-10-17 15:45 ` Felipe Balbi
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=20120928151051.GC4840@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 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).