From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2] ARM: AM43xx: hwmod: add DSS hwmod data
Date: Tue, 29 Jul 2014 04:07:54 -0700 [thread overview]
Message-ID: <20140729110754.GN29045@atomide.com> (raw)
In-Reply-To: <20140725165304.GD29132@saruman.home>
* Felipe Balbi <balbi@ti•com> [140725 09:55]:
> On Tue, Jul 22, 2014 at 09:14:20PM +0000, Paul Walmsley wrote:
> > On Tue, 17 Jun 2014, Tomi Valkeinen wrote:
> >
> > > From: Sathya Prakash M R <sathyap@ti•com>
> > >
> > > Add DSS hwmod data for AM43xx.
> > >
> > > Signed-off-by: Sathya Prakash M R <sathyap@ti•com>
> > > [tomi.valkeinen at ti.com: added missing dispc flags]
> > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti•com>
> > > Acked-by: Rajendra Nayak <rnayak@ti•com>
> >
> > This one didn't compile on an AM43xx-only build:
> >
> > ----
> > arch/arm/mach-omap2/built-in.o:(.data+0x3f2c): undefined reference to `omap2_dss_hwmod_class'
> > arch/arm/mach-omap2/built-in.o:(.data+0x405c): undefined reference to `omap2_rfbi_hwmod_class'
> > make: *** [vmlinux] Error 1
> > test_build: Tue Jul 22 13:48:50 MDT 2014: FAILED on omap2plus_defconfig_am43xx_only hwmod-a-v3.17
> > ----
> >
> > Have queued the following patch instead.
>
> queued for v3.17, I assume. Still not available from linux-next though.
Should be in linux-next now.
Tony
next prev parent reply other threads:[~2014-07-29 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 8:37 [PATCH v2] ARM: AM43xx: hwmod: add DSS hwmod data Tomi Valkeinen
2014-06-17 8:58 ` Tony Lindgren
2014-06-17 9:25 ` Tomi Valkeinen
2014-06-17 9:57 ` Tony Lindgren
2014-06-17 13:16 ` Felipe Balbi
2014-06-22 20:47 ` Paul Walmsley
2014-07-22 21:14 ` Paul Walmsley
2014-07-25 16:53 ` Felipe Balbi
2014-07-29 11:07 ` Tony Lindgren [this message]
2014-07-30 12:09 ` Tomi Valkeinen
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=20140729110754.GN29045@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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