From: mathieu.poirier@linaro.org (mathieu.poirier at linaro.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] omap randconfig fixes for v3.3
Date: Fri, 23 Mar 2012 11:13:47 -0600 [thread overview]
Message-ID: <1332522836-29517-1-git-send-email-mathieu.poirier@linaro.org> (raw)
From: "Arnd Bergmann" <arnd@arndb.de>
The following is a set of patches that have been sent
out during the 3.1 cycle that were not acked or merged.
Sending again for completeness.
Tony, please pull if there are no objections:
The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
Linux 3.3 (2012-03-18 16:15:34 -0700)
are available in the git repository at:
git://git.linaro.org/people/mpoirier/linux.git randconfig-omap
Arnd Bergmann (8):
arm/omap: enable building omap2 without omap2420/2430
omap: fix visibility of omap2_mbox_iva_priv
ARM: omap2+: fix building without i2c
tty/serial/omap: console can only be built-in
omap2: select twl4030 support on boards that need it
omap2plus: ensure that one of omap2/3/4 is selected
arm: OMAP depends on MMU
ARM: omap: select CPU_FREQ_TABLE where needed
Russell King (1):
ARM: omap2/n8x0: work around modular omap mmc
arch/arm/Kconfig | 1 +
arch/arm/mach-omap2/Kconfig | 19 +++++++++++++++++++
arch/arm/mach-omap2/board-n8x0.c | 6 ++++--
arch/arm/mach-omap2/mailbox.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2 +-
arch/arm/plat-omap/Kconfig | 5 +++++
arch/arm/plat-omap/include/plat/multi.h | 5 +++++
drivers/tty/serial/Kconfig | 2 +-
11 files changed, 40 insertions(+), 8 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-03-23 17:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 17:13 mathieu.poirier at linaro.org [this message]
2012-03-23 17:13 ` [PATCH 1/9] arm/omap: enable building omap2 without omap2420/2430 mathieu.poirier at linaro.org
2012-03-23 17:13 ` [PATCH 2/9] omap: fix visibility of omap2_mbox_iva_priv mathieu.poirier at linaro.org
2012-03-23 18:30 ` Tony Lindgren
2012-03-23 17:13 ` [PATCH 3/9] ARM: omap2/n8x0: work around modular omap mmc mathieu.poirier at linaro.org
2012-03-23 17:29 ` Tony Lindgren
2012-03-24 9:23 ` Russell King - ARM Linux
2012-03-23 17:13 ` [PATCH 4/9] ARM: omap2+: fix building without i2c mathieu.poirier at linaro.org
2012-03-23 17:22 ` Tony Lindgren
2012-03-23 17:13 ` [PATCH 5/9] tty/serial/omap: console can only be built-in mathieu.poirier at linaro.org
2012-03-23 18:33 ` Tony Lindgren
2012-03-23 17:13 ` [PATCH 6/9] omap2: select twl4030 support on boards that need it mathieu.poirier at linaro.org
2012-03-23 17:13 ` [PATCH 7/9] omap2plus: ensure that one of omap2/3/4 is selected mathieu.poirier at linaro.org
2012-03-23 17:28 ` Tony Lindgren
2012-03-23 17:38 ` Arnd Bergmann
2012-03-23 18:14 ` Tony Lindgren
2012-03-23 17:13 ` [PATCH 8/9] arm: OMAP depends on MMU mathieu.poirier at linaro.org
2012-03-23 17:13 ` [PATCH 9/9] ARM: omap: select CPU_FREQ_TABLE where needed mathieu.poirier at linaro.org
2012-03-23 18:27 ` Tony Lindgren
2012-03-26 23:09 ` Kevin Hilman
2012-03-29 17:28 ` [PATCH 0/9] omap randconfig fixes for v3.3 Tony Lindgren
2012-05-07 19:07 ` 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=1332522836-29517-1-git-send-email-mathieu.poirier@linaro.org \
--to=mathieu.poirier@linaro.org \
--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).