From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP: Trivial driver changes to remove include plat/cpu.h
Date: Wed, 17 Oct 2012 11:13:31 -0700 [thread overview]
Message-ID: <20121017181330.GV15569@atomide.com> (raw)
In-Reply-To: <20121016000722.GH15569@atomide.com>
* Tony Lindgren <tony@atomide.com> [121015 17:09]:
> * Tony Lindgren <tony@atomide.com> [121009 17:21]:
> > * P?ter Ujfalusi <peter.ujfalusi@ti.com> [121009 02:03]:
> > > On 10/08/2012 07:35 PM, Tony Lindgren wrote:
> > >
> > > > - omap-dma.c and omap-pcm.c can test the arch locally as
> > > > omap1 and omap2 cannot be compiled together because of
> > > > conflicting compiler flags
> > >
> > > > sound/soc/omap/omap-pcm.c | 9 +++++++--
> > >
> > > Tony: is this going to be included in 3.7?
> >
> > Hmm I guess we could try to get this out of the way
> > to cut down the dependencies. Let's if maintainers
> > of the other affected drivers this is OK for the
> > -rc series.
>
> It seems that nobody needs these until for v3.8, so I'll
> be applying this into omap-for-v3.8/cleanup-headers-prepare
> branch soon.
>
> Anybody else care to ack?
OK pushed out now with just that patch in the branch in case
driver branches need to merge it in too to avoid conflicts.
Regards,
Tony
next prev parent reply other threads:[~2012-10-17 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 17:35 [PATCH 0/2] omap plat/cpu.h removal for v3.8 merge window Tony Lindgren
2012-10-08 17:35 ` [PATCH 1/2] ARM: OMAP: Trivial driver changes to remove include plat/cpu.h Tony Lindgren
2012-10-08 18:09 ` Tony Lindgren
2012-10-09 6:20 ` Jarkko Nikula
2012-10-09 9:03 ` Péter Ujfalusi
2012-10-10 0:19 ` Tony Lindgren
2012-10-16 0:07 ` Tony Lindgren
2012-10-17 18:13 ` Tony Lindgren [this message]
2012-10-08 17:36 ` [PATCH 2/2] ARM: OMAP: Split plat/cpu.h into local soc.h for mach-omap1 and mach-omap2 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=20121017181330.GV15569@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).