On 04/04/13 17:12, Richard Weinberger wrote:
> Fair point. I'll add such a printk() to my patch and resend.
Also take a look at FW_BUG.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vg
Am 04.04.2013 18:00, schrieb Luck, Tony:
Some (broken?) EFI implementations return always a MaximumVariableSize of 0,
check against max_size only if it is non-zero.
The spec doesn't say that zero has any special meaning - so if an implementation
returns max_size == 0 but lets you set a variable
> Some (broken?) EFI implementations return always a MaximumVariableSize of 0,
> check against max_size only if it is non-zero.
The spec doesn't say that zero has any special meaning - so if an implementation
returns max_size == 0 but lets you set a variable to a size > 0, then I don't
think
ther
Some (broken?) EFI implementations return always a MaximumVariableSize of 0,
check against max_size only if it is non-zero.
Signed-off-by: Richard Weinberger
---
drivers/firmware/efivars.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/efivars.c b/drivers/
4 matches
Mail list logo