From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] ST-Ericsson Device Tree patches
Date: Tue, 27 Nov 2012 12:31:22 +0000 [thread overview]
Message-ID: <201211271231.23121.arnd@arndb.de> (raw)
In-Reply-To: <20121127111540.GC2013@gmail.com>
On Tuesday 27 November 2012, Lee Jones wrote:
> The following changes since commit 8f0d8163b50e01f398b14bcd4dc039ac5ab18d64:
>
> Linux 3.7-rc3 (2012-10-28 12:24:48 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/ljones/linux-3.0-ux500.git ste-dt-for-next
>
> for you to fetch changes up to e13316d60658aee7987b51025f342649baa33487:
>
> ARM: ux500: Rename dbx500 cpufreq code to be more generic (2012-11-27 10:58:57 +0000)
Pulled into next/dt and updated the ux500/dt branch to the latest head. Thanks!
Olof, just to clarify: there are 43 patches listed in the pull request, but there
are actually just 5 patches that were not there before. As discussed with Lee on
#linaro-kernel, this fixes a long-standing build error in for-next u8500_defconfig,
but does not fix the problem of a couple of duplicate patch IDs that still have in
the ux500/dt branch. I could not come up with a way that would actually improve
the situation rather than introduce other problems.
Arnd
prev parent reply other threads:[~2012-11-27 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 16:28 [GIT PULL] ST-Ericsson Device Tree patches Lee Jones
2012-11-21 9:20 ` Olof Johansson
2012-11-26 16:07 ` Lee Jones
2012-11-26 17:49 ` Arnd Bergmann
2012-11-27 9:03 ` Lee Jones
2012-11-27 11:15 ` [GIT PULL v3] " Lee Jones
2012-11-27 12:31 ` Arnd Bergmann [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=201211271231.23121.arnd@arndb.de \
--to=arnd@arndb.de \
--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).