From: sshtylyov@mvista•com (Sergei Shtylyov)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] initramfs: handle trailing junk after valid image
Date: Mon, 06 Aug 2012 23:05:07 +0400 [thread overview]
Message-ID: <50201563.2020509@mvista.com> (raw)
In-Reply-To: <20120806093251.0528E77A0D@aristotle.killerwolves.net>
Hello.
On 08/06/2012 01:32 PM, Ben Peddell wrote:
> The initramfs handling since commit df37bd15 has been rejecting
Please also specify the summary of that commit in parens.
> valid images that have garbage after them. For example, on an
> architecture where the initramfs address and size are specified
> as a kernel parameter (specifically unicore32 and arm), specifying
> e.g. initrd=0x01000000,4M will not work unless the image is padded
> with nulls to 4MiB. This is unlikely to occur if the user is using
> this parameter to work around a bug in the bootloader.
You didn't sign off the patchs, so it can't br applied.
WBR, Sergei
next prev parent reply other threads:[~2012-08-06 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 23:12 problems with external initramfs passed to device tree kernel John Linn
2012-08-06 9:25 ` Ben Peddell
2012-08-06 9:32 ` [PATCH] initramfs: handle trailing junk after valid image Ben Peddell
2012-08-06 19:05 ` Sergei Shtylyov [this message]
2012-08-07 2:02 ` [PATCH 1/1] initramfs: handle trailing junk after valid image (try 2) Ben Peddell
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=50201563.2020509@mvista.com \
--to=sshtylyov@mvista$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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