All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH ] omap4: Move SOC specific code from board file
Date: Tue, 11 May 2010 17:12:10 -0700	[thread overview]
Message-ID: <20100512001209.GT13931@atomide.com> (raw)
In-Reply-To: <1272695817-5973-1-git-send-email-santosh.shilimkar@ti.com>

* Santosh Shilimkar <santosh.shilimkar@ti.com> [100430 23:32]:
> This patch moves OMAP4 soc specific code from 4430sdp board file.
> The change is necessary so that newer board support can be added
> with minimal changes. This will be also problematic for
> multi-board, multi-omap builds.
> 
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> ---
> (Because veger issue this one never made to the list )
> Boot tested with regular and multi-omap defconfig on OMAP4430 and
> OMAP3430 SDPs. Needs Tony's sram fix to make multi-omap boot on OMAP4.

I'll apply this into omap for-next.

Regards,

Tony

      reply	other threads:[~2010-05-12  0:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01  6:36 [PATCH ] omap4: Move SOC specific code from board file Santosh Shilimkar
2010-05-12  0:12 ` Tony Lindgren [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=20100512001209.GT13931@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.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.