From: Tony Lindgren <tony@atomide.com>
To: Tom Rini <trini@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: OMAP2+: omap2plus_defconfig: Enable appended DTB support
Date: Thu, 4 Jul 2013 05:09:04 -0700 [thread overview]
Message-ID: <20130704120903.GN5523@atomide.com> (raw)
In-Reply-To: <1372684393-19025-1-git-send-email-trini@ti.com>
* Tom Rini <trini@ti.com> [130701 06:19]:
> As this config must support boards which cannot support separate device
> trees, enable support for appended ones.
This can cause things to go wrong when DTB is not appended for mistaking the
memory as an appended DTB, especially when doing a warm reset. But as we need
this in practise for older platforms, let's add it.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: omap2plus_defconfig: Enable appended DTB support
Date: Thu, 4 Jul 2013 05:09:04 -0700 [thread overview]
Message-ID: <20130704120903.GN5523@atomide.com> (raw)
In-Reply-To: <1372684393-19025-1-git-send-email-trini@ti.com>
* Tom Rini <trini@ti.com> [130701 06:19]:
> As this config must support boards which cannot support separate device
> trees, enable support for appended ones.
This can cause things to go wrong when DTB is not appended for mistaking the
memory as an appended DTB, especially when doing a warm reset. But as we need
this in practise for older platforms, let's add it.
Regards,
Tony
next prev parent reply other threads:[~2013-07-04 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 13:13 [PATCH] ARM: OMAP2+: omap2plus_defconfig: Enable appended DTB support Tom Rini
2013-07-01 13:13 ` Tom Rini
2013-07-04 12:09 ` Tony Lindgren [this message]
2013-07-04 12:09 ` 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=20130704120903.GN5523@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=trini@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.