Re: [PATCH v2 0/6] Chainsaw efivars.c

2013-04-17 Thread Matt Fleming
On 04/17/2013 01:30 AM, Tom Gundersen wrote: > Hi Matt, > > On Tue, Apr 16, 2013 at 11:41 PM, Matt Fleming wrote: >> This patch series introduces the new efivar_entry API, and splits out the >> major >> parts of efivars.c into new files. In particular, having the efivarfs code >> under fs/ allow

Re: [PATCH v2 0/6] Chainsaw efivars.c

2013-04-16 Thread Tom Gundersen
Hi Matt, On Tue, Apr 16, 2013 at 11:41 PM, Matt Fleming wrote: > This patch series introduces the new efivar_entry API, and splits out the > major > parts of efivars.c into new files. In particular, having the efivarfs code > under fs/ allows building an efivarfs.ko module, which means mount(8)

[PATCH v2 0/6] Chainsaw efivars.c

2013-04-16 Thread Matt Fleming
From: Matt Fleming drivers/firmware/efivars.c has grown pretty large and is ~2K lines. Inside efivars.c there's currently, o code for handling EFI variables at the firmware-level o sysfs code for exposing EFI variables o a new EFI variable filesystem o a persistent storage backend all