From: Tony Lindgren <tony@atomide.com>
To: Sricharan R <r.sricharan@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ARM: multi_v7: Add OMAP with ramdisk config bits
Date: Tue, 25 Jun 2013 00:02:04 -0700 [thread overview]
Message-ID: <20130625070203.GA5523@atomide.com> (raw)
In-Reply-To: <51C858B4.2020106@ti.com>
* Sricharan R <r.sricharan@ti.com> [130624 07:39]:
> Hi,
> On Tuesday 18 June 2013 08:14 PM, Santosh Shilimkar wrote:
> > On Tuesday 18 June 2013 04:24 AM, Tony Lindgren wrote:
> >> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130612 14:14]:
> >>> Add ramdisk fileystem related options which lets OMAP5 and Keystone
> >>> SOCs to boot till shell with multi_v7_config.
> >> Please add also other v7 omaps.
> >>
> > Should have done first place. Sorry.
> > Will update other machines and after testing, repost it.
> >
> > Regards,
> > Santosh
> >
> Since CONFIG_ARCH_OMAP2PLUS=y is set in the patch,
> OMAP3, OMAP4 are getting enabled by default.
>
> I tested OMAP4 PANDA on mainline + multi_v7_config + above patch
> and it booted up fine.
OK thanks for testing. Those default y things will be going
away, but we can update both defconfigs after that.
Acked-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7: Add OMAP with ramdisk config bits
Date: Tue, 25 Jun 2013 00:02:04 -0700 [thread overview]
Message-ID: <20130625070203.GA5523@atomide.com> (raw)
In-Reply-To: <51C858B4.2020106@ti.com>
* Sricharan R <r.sricharan@ti.com> [130624 07:39]:
> Hi,
> On Tuesday 18 June 2013 08:14 PM, Santosh Shilimkar wrote:
> > On Tuesday 18 June 2013 04:24 AM, Tony Lindgren wrote:
> >> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130612 14:14]:
> >>> Add ramdisk fileystem related options which lets OMAP5 and Keystone
> >>> SOCs to boot till shell with multi_v7_config.
> >> Please add also other v7 omaps.
> >>
> > Should have done first place. Sorry.
> > Will update other machines and after testing, repost it.
> >
> > Regards,
> > Santosh
> >
> Since CONFIG_ARCH_OMAP2PLUS=y is set in the patch,
> OMAP3, OMAP4 are getting enabled by default.
>
> I tested OMAP4 PANDA on mainline + multi_v7_config + above patch
> and it booted up fine.
OK thanks for testing. Those default y things will be going
away, but we can update both defconfigs after that.
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2013-06-25 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 21:08 [PATCH] ARM: multi_v7: Add OMAP with ramdisk config bits Santosh Shilimkar
2013-06-12 21:08 ` Santosh Shilimkar
2013-06-18 8:24 ` Tony Lindgren
2013-06-18 8:24 ` Tony Lindgren
2013-06-18 14:44 ` Santosh Shilimkar
2013-06-18 14:44 ` Santosh Shilimkar
2013-06-24 14:33 ` Sricharan R
2013-06-24 14:33 ` Sricharan R
2013-06-24 14:49 ` Sricharan R
2013-06-24 14:49 ` Sricharan R
2013-06-25 7:02 ` Tony Lindgren [this message]
2013-06-25 7:02 ` Tony Lindgren
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=20130625070203.GA5523@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=r.sricharan@ti.com \
--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.