From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/6] omap cleanup fixes for v3.8 merge window
Date: Mon, 12 Nov 2012 17:05:40 -0800 [thread overview]
Message-ID: <20121113010539.GZ6801@atomide.com> (raw)
In-Reply-To: <pull-1352768345-815774>
* Tony Lindgren <ton@atomide.com> [121112 17:01]:
> The following changes since commit edf8dde393f879fc2d8c22d4bc01ff8d37b80e1a:
>
> Merge branch 'linus' into omap-for-v3.8/cleanup-headers-prepare-multiplatform-v3 (2012-11-09 14:58:01 -0800)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.8/cleanup-fixes-signed
>
> for you to fetch changes up to e05cf58d50e3ce3601ebf753728eee0df759e38f:
>
> ARM: OMAP2+: remove duplicated include from board-overo.c (2012-11-12 14:02:48 -0800)
>
> ----------------------------------------------------------------
> Minor fixes to the clean-up done for ARM common multi-platform
> support for omaps.
FYI, some of the pull requests after this one may break
compile for omap2plus_defconfig when merging them in.
I suggest you pull requests 2 - 6 with --no-commit option and
make sure it builds after each pull if you have a chance.
Or I can follow up with fixes if needed.
If in doubt, I've pushded omap-for-v3.8/tmp-merge that's a
merge of v3.7-rc5 + recently pulled omap fixes + these pull
requests merged together for reference.
Cheers,
Tony
next parent reply other threads:[~2012-11-13 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pull-1352768345-815774>
2012-11-13 1:05 ` Tony Lindgren [this message]
2012-11-13 17:44 ` [GIT PULL 1/6] omap cleanup fixes for v3.8 merge window Tony Lindgren
2012-11-13 19:03 ` Tony Lindgren
[not found] <pull-1352828737-887235>
2012-11-15 16:27 ` Arnd Bergmann
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=20121113010539.GZ6801@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).