From: rnayak@ti•com (Rajendra Nayak)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] Fix crash on OMAP with CONFIG_DEBUG_SLAB
Date: Thu, 14 Mar 2013 18:15:37 +0530 [thread overview]
Message-ID: <5141C671.9070504@ti.com> (raw)
In-Reply-To: <1363264618-5071-1-git-send-email-rnayak@ti.com>
Missed out Mike, copied now.
On Thursday 14 March 2013 06:06 PM, Rajendra Nayak wrote:
> These patches mainly fix the crash that was reported with
> CONFIG_DEBUG_SLAB enabled on OMAPs, due to the early clock
> initializations.
>
> Tested on Panda ES (omap4460), beagle Xm (omap3630) and
> BeagleBoneBlack (AM335x)
>
> Rajendra Nayak (2):
> ARM: OMAP2+: clocks: Have consistent naming for parent name arrays
> ARM: OMAP2+: clocks: Pass static parent pointers to common clock core
>
> arch/arm/mach-omap2/cclock2420_data.c | 314 ++++++++++-------
> arch/arm/mach-omap2/cclock2430_data.c | 332 ++++++++++--------
> arch/arm/mach-omap2/cclock33xx_data.c | 74 +++-
> arch/arm/mach-omap2/cclock3xxx_data.c | 599 ++++++++++++++++++---------------
> arch/arm/mach-omap2/cclock44xx_data.c | 240 ++++++++++---
> arch/arm/mach-omap2/clock.h | 15 +-
> 6 files changed, 965 insertions(+), 609 deletions(-)
>
prev parent reply other threads:[~2013-03-14 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 12:36 [PATCH 0/2] Fix crash on OMAP with CONFIG_DEBUG_SLAB Rajendra Nayak
2013-03-14 12:36 ` [PATCH 2/2] ARM: OMAP2+: clocks: Pass static parent pointers to common clock core Rajendra Nayak
2013-03-14 17:06 ` Tony Lindgren
2013-03-15 12:27 ` Rajendra Nayak
2013-03-15 16:20 ` Tony Lindgren
2013-03-18 8:20 ` Rajendra Nayak
2013-03-18 16:37 ` Tony Lindgren
2013-03-19 1:23 ` Mike Turquette
2013-03-19 5:16 ` Rajendra Nayak
2013-03-14 12:45 ` Rajendra Nayak [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=5141C671.9070504@ti.com \
--to=rnayak@ti$(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