All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Janboe Ye <yuan-bo.ye@motorola.com>,
	linux-omap@vger.kernel.org, mans@mansr.com,
	khilman@deeprootsystems.com,
	Hong Mei Li <hong-mei.li@motorola.com>
Subject: Re: [PATCH] fix omap3 sram virtual addres overlap vmalloc space after increasing vmalloc size
Date: Wed, 5 Aug 2009 16:40:55 +0300	[thread overview]
Message-ID: <20090805134055.GH7374@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907211009240.19170@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [090721 19:10]:
> On Tue, 21 Jul 2009, Janboe Ye wrote:
> 
> > Thanks, Paul
> > 
> > Tony
> > 
> > Is there some issue about this patch?
> 
> Tony's on vacation right now, so you shouldn't expect a response from him 
> until he returns.
> 
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg14015.html

I've added this patch to my omap-fixes queue, had to apply it manually
because of the omap4 defines.

Tony

> 
> 
> - Paul
> 
> > 
> > Thanks
> > 
> > Janboe Ye
> > 
> > On Fri, 2009-07-17 at 16:04 -0600, Paul Walmsley wrote:
> > > On Thu, 16 Jul 2009, Janboe Ye wrote:
> > > 
> > > > resend for mini coding style fixing
> > > > 
> > > > commit e85c205ac1427f2405021a36f083280ff0d0a35e increase vmalloc size.
> > > > vmalloc space will overlap with OMAP3 sram virtual address.
> > > 
> > > Makes sense to me.  I'm not sure how we missed this in the original patch.
> > > 
> > > Reviewed-by: Paul Walmsley <paul@pwsan.com>
> > > 
> > > - Paul
> > > 
> > > > 
> > > > Signed-off-by: Li Hong Mei <hong-mei.li@motorola.com>
> > > > Signed-off-by: Janboe Ye <yuan-bo.ye@motorola.com>
> > > > ---
> > > >  arch/arm/plat-omap/sram.c |    4 ++--
> > > >  1 files changed, 2 insertions(+), 2 deletions(-)
> > > > 
> > > > diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
> > > > index a2e60e7..755ccaa 100644
> > > > --- a/arch/arm/plat-omap/sram.c
> > > > +++ b/arch/arm/plat-omap/sram.c
> > > > @@ -41,9 +41,9 @@
> > > >  #define OMAP2_SRAM_VA          0xe3000000
> > > >  #define OMAP2_SRAM_PUB_VA      (OMAP2_SRAM_VA + 0x800)
> > > >  #define OMAP3_SRAM_PA           0x40200000
> > > > -#define OMAP3_SRAM_VA           0xd7000000
> > > > +#define OMAP3_SRAM_VA           0xe3000000
> > > >  #define OMAP3_SRAM_PUB_PA       0x40208000
> > > > -#define OMAP3_SRAM_PUB_VA       0xd7008000
> > > > +#define OMAP3_SRAM_PUB_VA       (OMAP3_SRAM_VA + 0x8000)
> > > > 
> > > >  #if defined(CONFIG_ARCH_OMAP24XX) || defined(CONFIG_ARCH_OMAP34XX)
> > > >  #define SRAM_BOOTLOADER_SZ     0x00
> > > > 
> > > 
> > > 
> > > - Paul
> > 
> 
> 
> - Paul

  reply	other threads:[~2009-08-05 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 22:47 [PATCH] fix omap3 sram virtual addres overlap vmalloc space after increasing vmalloc size Janboe Ye
2009-07-17 22:04 ` Paul Walmsley
2009-07-21 16:02   ` Janboe Ye
2009-07-21 16:10     ` Paul Walmsley
2009-08-05 13:40       ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-16 22:38 Janboe Ye

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=20090805134055.GH7374@atomide.com \
    --to=tony@atomide.com \
    --cc=hong-mei.li@motorola.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=paul@pwsan.com \
    --cc=yuan-bo.ye@motorola.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.