Re: [PATCH 0/2] nvmem: meson-efuse: add write support

Jerome Brunet writes: > This changeset adds write support to meson efuse driver. > The first patch just changes the way the nvmem data are allocated w/o > any functional changes. The second patches actually adds write support. > > The memory being an OTP, it is safer if it

Re: [PATCH 0/2] nvmem: meson-efuse: add write support

Jerome Brunet writes: > This changeset adds write support to meson efuse driver. > The first patch just changes the way the nvmem data are allocated w/o > any functional changes. The second patches actually adds write support. > > The memory being an OTP, it is safer if it remains read-only by

Re: [PATCH 0/2] nvmem: meson-efuse: add write support

On 19/04/18 15:13, Jerome Brunet wrote: On Fri, 2018-03-16 at 16:01 +0100, Jerome Brunet wrote: This changeset adds write support to meson efuse driver. The first patch just changes the way the nvmem data are allocated w/o any functional changes. The second patches actually adds write

Re: [PATCH 0/2] nvmem: meson-efuse: add write support

On 19/04/18 15:13, Jerome Brunet wrote: On Fri, 2018-03-16 at 16:01 +0100, Jerome Brunet wrote: This changeset adds write support to meson efuse driver. The first patch just changes the way the nvmem data are allocated w/o any functional changes. The second patches actually adds write

Re: [PATCH 0/2] nvmem: meson-efuse: add write support

On Fri, 2018-03-16 at 16:01 +0100, Jerome Brunet wrote: > This changeset adds write support to meson efuse driver. > The first patch just changes the way the nvmem data are allocated w/o > any functional changes. The second patches actually adds write support. > > The memory being an OTP, it is

Re: [PATCH 0/2] nvmem: meson-efuse: add write support

On Fri, 2018-03-16 at 16:01 +0100, Jerome Brunet wrote: > This changeset adds write support to meson efuse driver. > The first patch just changes the way the nvmem data are allocated w/o > any functional changes. The second patches actually adds write support. > > The memory being an OTP, it is

[PATCH 0/2] nvmem: meson-efuse: add write support

This changeset adds write support to meson efuse driver. The first patch just changes the way the nvmem data are allocated w/o any functional changes. The second patches actually adds write support. The memory being an OTP, it is safer if it remains read-only by default, which is why I also

[PATCH 0/2] nvmem: meson-efuse: add write support

This changeset adds write support to meson efuse driver. The first patch just changes the way the nvmem data are allocated w/o any functional changes. The second patches actually adds write support. The memory being an OTP, it is safer if it remains read-only by default, which is why I also