Hi Joe
On Wed, Nov 14, 2012 at 4:31 PM, Joe Perches wrote:
> On Tue, 2012-11-13 at 14:50 +0800, Andrew Cooks wrote:
>> The boot_delay parameter affects all printk(), even if the log level
>> prevents visible output from the call. It results in delays greater
>> than the user intended without
Hi Joe
On Wed, Nov 14, 2012 at 4:31 PM, Joe Perches j...@perches.com wrote:
On Tue, 2012-11-13 at 14:50 +0800, Andrew Cooks wrote:
The boot_delay parameter affects all printk(), even if the log level
prevents visible output from the call. It results in delays greater
than the user intended
On 11/12/2012 10:50 PM, Andrew Cooks wrote:
> The boot_delay parameter affects all printk(), even if the log level
> prevents visible output from the call. It results in delays greater
> than the user intended without purpose.
>
> This patch changes the behaviour of boot_delay to only delay
On 11/12/2012 10:50 PM, Andrew Cooks wrote:
The boot_delay parameter affects all printk(), even if the log level
prevents visible output from the call. It results in delays greater
than the user intended without purpose.
This patch changes the behaviour of boot_delay to only delay output.
The boot_delay parameter affects all printk(), even if the log level
prevents visible output from the call. It results in delays greater
than the user intended without purpose.
This patch changes the behaviour of boot_delay to only delay output.
Signed-off-by: Andrew Cooks
---
The boot_delay parameter affects all printk(), even if the log level
prevents visible output from the call. It results in delays greater
than the user intended without purpose.
This patch changes the behaviour of boot_delay to only delay output.
Signed-off-by: Andrew Cooks aco...@gmail.com
---
6 matches
Mail list logo