From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] PM: Changed secure RAM storage size from 0x8000 to 0x803F
Date: Thu, 13 Nov 2008 05:54:14 -0800 [thread overview]
Message-ID: <87fxlvlojd.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1226576465-14387-1-git-send-email-tero.kristo@nokia.com> (Tero Kristo's message of "Thu\, 13 Nov 2008 13\:41\:05 +0200")
Tero Kristo <tero.kristo@nokia.com> writes:
> Without this, causes some random crashes related to memory management.
>
> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
Looks like this is against pm-20081106. Pulling into next PM branch.
Kevin
> ---
> arch/arm/mach-omap2/pm34xx.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 0df3245..58d0479 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -883,7 +883,7 @@ int __init omap3_pm_init(void)
>
> if (omap_type() != OMAP2_DEVICE_TYPE_GP) {
> omap3_secure_ram_storage =
> - kmalloc(0x8000, GFP_KERNEL);
> + kmalloc(0x803F, GFP_KERNEL);
> if (!omap3_secure_ram_storage)
> printk(KERN_ERR "Memory allocation failed when"
> "allocating for secure sram context\n");
> --
> 1.5.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-11-13 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 11:41 [PATCH] PM: Changed secure RAM storage size from 0x8000 to 0x803F Tero Kristo
2008-11-13 13:54 ` Kevin Hilman [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=87fxlvlojd.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tero.kristo@nokia.com \
/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.