Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-14 Thread joeyli
於 二,2013-05-14 於 08:16 +0100,Matt Fleming 提到: > On 05/14/2013 05:36 AM, joeyli wrote: > > I found the "[PATCH] x86, efi: initial the local variable of DataSize to > > zero" lost in urgent branch, and it also didn't in Linus's v3.10-rc1. > > > > Did this patch move to other branch? > > It appears

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-14 Thread Matt Fleming
On 05/14/2013 05:36 AM, joeyli wrote: > I found the "[PATCH] x86, efi: initial the local variable of DataSize to > zero" lost in urgent branch, and it also didn't in Linus's v3.10-rc1. > > Did this patch move to other branch? It appears I dropped this patch when doing the rebase against -rc1.

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-14 Thread Matt Fleming
On 05/14/2013 05:36 AM, joeyli wrote: I found the [PATCH] x86, efi: initial the local variable of DataSize to zero lost in urgent branch, and it also didn't in Linus's v3.10-rc1. Did this patch move to other branch? It appears I dropped this patch when doing the rebase against -rc1. I'm

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-14 Thread joeyli
於 二,2013-05-14 於 08:16 +0100,Matt Fleming 提到: On 05/14/2013 05:36 AM, joeyli wrote: I found the [PATCH] x86, efi: initial the local variable of DataSize to zero lost in urgent branch, and it also didn't in Linus's v3.10-rc1. Did this patch move to other branch? It appears I dropped

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-13 Thread joeyli
Hi Matt, 於 一,2013-05-13 於 20:21 +0100,Matt Fleming 提到: > On 05/10/2013 11:29 AM, Lingzhu Xiang wrote: > > Previously in 1fa7e69 efi_status_to_err() translated firmware status > > EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to > > avoid confusion. After refactoring in

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-13 Thread Matt Fleming
On 05/10/2013 11:29 AM, Lingzhu Xiang wrote: > Previously in 1fa7e69 efi_status_to_err() translated firmware status > EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to > avoid confusion. After refactoring in e14ab23, it is also used in other > places where the translation may be

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-13 Thread Matt Fleming
On 05/10/2013 11:29 AM, Lingzhu Xiang wrote: Previously in 1fa7e69 efi_status_to_err() translated firmware status EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to avoid confusion. After refactoring in e14ab23, it is also used in other places where the translation may be

Re: [PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-13 Thread joeyli
Hi Matt, 於 一,2013-05-13 於 20:21 +0100,Matt Fleming 提到: On 05/10/2013 11:29 AM, Lingzhu Xiang wrote: Previously in 1fa7e69 efi_status_to_err() translated firmware status EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to avoid confusion. After refactoring in e14ab23, it is

[PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-10 Thread Lingzhu Xiang
Previously in 1fa7e69 efi_status_to_err() translated firmware status EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to avoid confusion. After refactoring in e14ab23, it is also used in other places where the translation may be unnecessary. So move the translation to efivarfs

[PATCH] efivarfs: Never return ENOENT from firmware again

2013-05-10 Thread Lingzhu Xiang
Previously in 1fa7e69 efi_status_to_err() translated firmware status EFI_NOT_FOUND to -EIO instead of -ENOENT for efivarfs operations to avoid confusion. After refactoring in e14ab23, it is also used in other places where the translation may be unnecessary. So move the translation to efivarfs