Am 20.12.2011 19:49, schrieb Göran Weinholt: > Alexander Graf <ag...@suse.de> writes: > >> Yes, this patch makes things work again :). Thanks a lot! >> >> The only thing I could nitpick on would be the coding style - checkpatch.pl >> complains :). Could you please resend with braces? >> Justin, Please also queue this for 1.0-stable when it comes in its final >> form. >> >> Tested-by: Alexander Graf <ag...@suse.de> > > Thanks for testing it. Here it is, with braces this time. > > > From 2a2df801d68a76fb2210e556652fb2e17e0f6711 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?G=C3=B6ran=20Weinholt?= <go...@weinholt.se> > Date: Tue, 20 Dec 2011 19:36:10 +0100 > Subject: [PATCH] multiboot: mh_load_end_addr and mh_bss_end_addr may be zero > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > There are two special cases in the address fields of the multiboot > format. If mh_load_end_addr is zero then the whole image file should > be loaded and if mh_bss_end_addr is zero then there is no bss segment. > With this change it is again possible to boot kernels where these > fields are zero. > > Signed-off-by: Göran Weinholt <go...@weinholt.se> > Tested-by: Alexander Graf <ag...@suse.de>
This doesn't seem to be applied yet. Can you resend it as a top-level email instead of deep in some thread where it may be missed? Kevin
