All of lore.kernel.org
 help / color / mirror / Atom feed
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] clk: Allow late cache allocation for clk->parents
Date: Tue, 12 Jun 2012 12:07:28 -0700	[thread overview]
Message-ID: <20120612190728.GI19410@gmail.com> (raw)
In-Reply-To: <1338973891-28719-3-git-send-email-rnayak@ti.com>

On 20120606-14:41, Rajendra Nayak wrote:
> Parent clocks for muxes are cached in clk->parents to
> avoid frequent lookups, however the cache allocation happens
> only during clock registeration and later clk_set_parent()
> assumes a cache space available and allocated.
> 
> This is not entirely true for platforms which do early clock
> registerations wherein the cache allocation using kzalloc
> could fail during clock registeration.
> 
> Allow cache allocation to happen later as part of clk_set_parent()
> to help such cases and avoid crashes assuming a cache being
> available.
> 
> While here also replace existing kmalloc() with kzalloc()
> in the file.
> 
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>

I've taken this patch into clk-next for testing.

Thanks,
Mike

WARNING: multiple messages have this Message-ID (diff)
From: Mike Turquette <mturquette@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] clk: Allow late cache allocation for clk->parents
Date: Tue, 12 Jun 2012 12:07:28 -0700	[thread overview]
Message-ID: <20120612190728.GI19410@gmail.com> (raw)
In-Reply-To: <1338973891-28719-3-git-send-email-rnayak@ti.com>

On 20120606-14:41, Rajendra Nayak wrote:
> Parent clocks for muxes are cached in clk->parents to
> avoid frequent lookups, however the cache allocation happens
> only during clock registeration and later clk_set_parent()
> assumes a cache space available and allocated.
> 
> This is not entirely true for platforms which do early clock
> registerations wherein the cache allocation using kzalloc
> could fail during clock registeration.
> 
> Allow cache allocation to happen later as part of clk_set_parent()
> to help such cases and avoid crashes assuming a cache being
> available.
> 
> While here also replace existing kmalloc() with kzalloc()
> in the file.
> 
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>

I've taken this patch into clk-next for testing.

Thanks,
Mike

  reply	other threads:[~2012-06-12 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  9:11 [PATCH 0/2] some minor clk fixes Rajendra Nayak
2012-06-06  9:11 ` Rajendra Nayak
2012-06-06  9:11 ` [PATCH 1/2] clk: cache parent clocks only for muxes Rajendra Nayak
2012-06-06  9:11   ` Rajendra Nayak
2012-06-06 10:47   ` Russell King - ARM Linux
2012-06-06 10:47     ` Russell King - ARM Linux
2012-06-12 19:04     ` Mike Turquette
2012-06-12 19:04       ` Mike Turquette
2012-06-13  4:39       ` Rajendra Nayak
2012-06-13  4:39         ` Rajendra Nayak
2012-06-06  9:11 ` [PATCH 2/2] clk: Allow late cache allocation for clk->parents Rajendra Nayak
2012-06-06  9:11   ` Rajendra Nayak
2012-06-12 19:07   ` Mike Turquette [this message]
2012-06-12 19:07     ` Mike Turquette

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=20120612190728.GI19410@gmail.com \
    --to=mturquette@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.