From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: arm-soc fixes for 3.8
Date: Thu, 20 Dec 2012 18:47:14 +0000 [thread overview]
Message-ID: <20121220184714.GB14363@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMgxXmXUW2RP_5AxJ6Z5sRBhFJ2CQz4S12MwXAb3=ibYOA@mail.gmail.com>
On Thu, Dec 20, 2012 at 10:08:42AM -0800, Olof Johansson wrote:
> On Thu, Dec 20, 2012 at 9:56 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Thu, Dec 20, 2012 at 08:38:14AM -0800, Olof Johansson wrote:
> >> One of the sunxi patches from the last pull request was misapplied (I
> >> realized what happened -- git am -s didn't apply cleanly so I had done it
> >> through regular patch, thus not catching the renames properly). Here's
> >> a fresh version of the pull request with a couple more OMAP and Samsung
> >> patches included.
> >>
> >> There's a chance that a couple of the OMAP patches will also go in through
> >> Russell, since my connectivity has been crap so far this trip and it
> >> causes build breaks for the platform. It's a branch pull from Tony,
> >> it should be a no-op either way.
> >
> > Olof,
> >
> > Not sure what's going on, but my recent pull from arm-soc for-next still
> > hasn't solved the OMAP build failures in my kbuild - I'm still getting:
> >
> > arch/arm/mach-omap2/timer.c: In function 'omap_get_timer_dt':
> > arch/arm/mach-omap2/timer.c:178:3: error: implicit declaration of function 'prom_add_property'
> > arch/arm/mach-omap2/i2c.c: In function 'omap_pm_set_max_mpu_wakeup_lat_compat':
> > arch/arm/mach-omap2/i2c.c:130:2: error: implicit declaration of function 'omap_pm_set_max_mpu_wakeup_lat'
>
> Yep, I forgot to bring the fixes branch into our for-next. Try again
> once it mirrors out, I just pushed out a rebuild of it. New top commit
> should be e691d77e8825054376b31e79a9b5f9fa79fe764d.
Yes, this looks much better, thanks.
prev parent reply other threads:[~2012-12-20 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 16:38 [GIT PULL v2] ARM: arm-soc fixes for 3.8 Olof Johansson
2012-12-20 16:49 ` Linus Torvalds
2012-12-20 17:28 ` Olof Johansson
2012-12-20 17:35 ` Tony Lindgren
2012-12-20 17:44 ` Linus Torvalds
2012-12-20 17:56 ` Russell King - ARM Linux
2012-12-20 18:08 ` Olof Johansson
2012-12-20 18:45 ` Tony Lindgren
2012-12-20 19:00 ` Linus Torvalds
2012-12-20 19:08 ` Tony Lindgren
2012-12-20 19:50 ` [PATCH] ARM: OMAP2+: Trivial fix for IOMMU merge issue (Re: [GIT PULL v2] ARM: arm-soc fixes for 3.8) Tony Lindgren
2012-12-21 2:43 ` [GIT PULL v2] ARM: arm-soc fixes for 3.8 Benjamin Herrenschmidt
2012-12-20 18:47 ` Russell King - ARM Linux [this message]
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=20121220184714.GB14363@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).