mirror of
git://projects.qi-hardware.com/xburst-tools.git
synced 2024-11-26 11:22:27 +02:00
phase2: block init buggy x
Is it really correct to set last_block_init to the next entry ? It would seem that the current (i.e., bogus) values are then just used without further ado. Untested. Not-Yet-Signed-off-by: Werner Almesberger <werner@openmoko.org>
This commit is contained in:
parent
f5798e6359
commit
9411e40603
@ -116,7 +116,7 @@ static int do_block_init(void)
|
|||||||
puts("block device init failed\n");
|
puts("block device init failed\n");
|
||||||
if (this_kernel->block_init != last_block_init)
|
if (this_kernel->block_init != last_block_init)
|
||||||
indicate(UI_IND_MOUNT_FAIL);
|
indicate(UI_IND_MOUNT_FAIL);
|
||||||
last_block_init = this_kernel[1].block_init;
|
last_block_init = NULL;
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
last_block_init = this_kernel->block_init;
|
last_block_init = this_kernel->block_init;
|
||||||
|
Loading…
Reference in New Issue
Block a user