From: Simon Horman <horms@verge.net.au>
To: Matthias Brugger <mbrugger@suse.com>
Cc: geoff@infradead.org, panand@redhat.com,
ard.biesheuvel@linaro.org, kexec@lists.infradead.org,
catalin.marinas@arm.com
Subject: Re: [PATCH] arm64: Fix initrd requierements
Date: Fri, 9 Dec 2016 08:59:46 +0100 [thread overview]
Message-ID: <20161209075941.GB30610@verge.net.au> (raw)
In-Reply-To: <1481127975-9156-1-git-send-email-mbrugger@suse.com>
On Wed, Dec 07, 2016 at 05:26:15PM +0100, Matthias Brugger wrote:
> The initrd doesn't need to be aligend to 1 GB, which breaks kexec for system with
> RAM <= 1 GB. Instead the memory size between the kernel start rounded down to 1 GB
> and the end of the initrd rounded up to 1 GB can't be bigger then 32 GB.
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
Thanks, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-12-09 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 16:26 [PATCH] arm64: Fix initrd requierements Matthias Brugger
2016-12-09 7:59 ` Simon Horman [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=20161209075941.GB30610@verge.net.au \
--to=horms@verge.net.au \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=geoff@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=mbrugger@suse.com \
--cc=panand@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox