Re: [PATCH 3/3] nvmem: core: Allow allocating several anonymous nvmem devices

2017-03-03 Thread Srinivas Kandagatla
On 02/03/17 19:50, Alban wrote: Currently the nvmem core expect the config to provide a name and ID that are then used to create the device name. When no device name is given 'nvmem' is used. However if there is several such anonymous devices they all get named 'nvmem0', which doesn't work. To

Re: [PATCH 3/3] nvmem: core: Allow allocating several anonymous nvmem devices

2017-03-02 Thread Moritz Fischer
On Thu, Mar 2, 2017 at 12:03 PM, Boris Brezillon wrote: > On Thu, 2 Mar 2017 20:50:23 +0100 > Alban wrote: > >> Currently the nvmem core expect the config to provide a name and ID >> that are then used to create the device name. When no device name is >> given 'nvmem' is used. However if there i

Re: [PATCH 3/3] nvmem: core: Allow allocating several anonymous nvmem devices

2017-03-02 Thread Boris Brezillon
On Thu, 2 Mar 2017 20:50:23 +0100 Alban wrote: > Currently the nvmem core expect the config to provide a name and ID > that are then used to create the device name. When no device name is > given 'nvmem' is used. However if there is several such anonymous > devices they all get named 'nvmem0', w

[PATCH 3/3] nvmem: core: Allow allocating several anonymous nvmem devices

2017-03-02 Thread Alban
Currently the nvmem core expect the config to provide a name and ID that are then used to create the device name. When no device name is given 'nvmem' is used. However if there is several such anonymous devices they all get named 'nvmem0', which doesn't work. To fix this problem use the ID from th