From: Tony Lindgren <tony@atomide.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-omap@vger.kernel.org
Subject: Re: Help needed with remaining plat headers
Date: Fri, 21 Sep 2012 11:46:45 -0700 [thread overview]
Message-ID: <20120921184644.GD28835@atomide.com> (raw)
In-Reply-To: <505C2E22.9020001@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [120921 02:07]:
> On 09/21/12 02:29, Tony Lindgren wrote:
> > Hi all,
> >
> > With the recent pull request I sent for v3.7, we now have pretty
> > much all the mach includes fixed up for omap2+ for single zImage
> > support.
> >
> > We still have quite a few plat headers that we need to sort
> > out manually.
> >
> > Please take a look at the following list, and reply to this
> > thread if you are working on patches moving one of the headers
> > in the list so we can coordinate things. The rules are simple
> > for most of them:
> >
> > 1. For driver related data, the header should now be in
> > include/linux/platform_data/*.h
Just to clarify this, these headers should only contain
the platform data shared between the SoC specific code and
driver. Things that are driver internal should be in the driver
specific header or moved to the driver. Things that are SoC
internal should be in the local *.[chS] files in the
arch/arm/mach-omap2 directory.
> > 2. For mach-omap2 specific things, the headers should be
> > in arch/arm/mach-omap2.
> >
> > 3. Drivers should not include anything from plat or mach.
> >
> > I'll be looking into getting rid of cpu.h etc for v3.8 merge
> > window, but won't be looking much at the driver related
> > headers. So some help would be appreciated here :)
> >
> > Regards,
> >
> > Tony
> >
> >
> > $ ls arch/arm/plat-omap/include/plat/
>
> [...]
>
> > timex.h
>
> I'll try to deal with this one,
> as it is related to the work I currently do for CONFIG_OMAP_32K_TIMER removal.
> Probably for v3.8 merge window.
OK great thanks,
Tony
next prev parent reply other threads:[~2012-09-21 18:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 23:29 Help needed with remaining plat headers Tony Lindgren
2012-09-21 9:06 ` Igor Grinberg
2012-09-21 18:46 ` Tony Lindgren [this message]
2012-09-27 9:57 ` Vutla, Lokesh
2012-09-27 19:58 ` Tony Lindgren
2012-09-28 8:54 ` Peter Ujfalusi
2012-09-28 10:05 ` Vutla, Lokesh
2012-09-27 10:07 ` Tomi Valkeinen
2012-09-27 19:57 ` Tony Lindgren
2012-09-27 20:26 ` Tony Lindgren
2012-09-27 20:31 ` Tony Lindgren
2012-09-27 20:33 ` Shilimkar, Santosh
2012-09-28 0:01 ` Tony Lindgren
2012-09-28 4:46 ` Mohammed, Afzal
2012-09-28 6:58 ` Vutla, Lokesh
2012-10-01 9:34 ` Peter Ujfalusi
2012-09-28 7:02 ` [PATCH] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h> Felipe Balbi
[not found] ` <1348815748-30072-1-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-09-28 15:13 ` Tony Lindgren
2012-09-28 15:19 ` Help needed with remaining plat headers Jon Hunter
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=20120921184644.GD28835@atomide.com \
--to=tony@atomide.com \
--cc=grinberg@compulab.co.il \
--cc=linux-omap@vger.kernel.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).