From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: vmlinux-xip.lds: assert that ROM and RAM don't overlap
Date: Tue, 16 Feb 2016 22:17:43 +0100 [thread overview]
Message-ID: <5611698.LJs5sAezys@wuerfel> (raw)
In-Reply-To: <HK2PR06MB05619656241BFD0A9165B6C28AAD0@HK2PR06MB0561.apcprd06.prod.outlook.com>
On Tuesday 16 February 2016 19:18:51 Chris Brandt wrote:
>
> This looks fine to me. I see no issues with it.
> Of course, this is for systems with a much tighter device memory layout than what I usually use.
The overlap should only happen when you have really large kernel images
over 16MB of readonly .text+.rodata, and I would assume this rarely happens
in practice.
Arnd
prev parent reply other threads:[~2016-02-16 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 12:06 [PATCH v2] ARM: vmlinux-xip.lds: assert that ROM and RAM don't overlap Ard Biesheuvel
2016-02-16 19:18 ` Chris Brandt
2016-02-16 21:17 ` Arnd Bergmann [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=5611698.LJs5sAezys@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox