On 17/09/2019 08:57, Arnd Bergmann wrote:
On Mon, Sep 9, 2019 at 3:45 PM Sebastian Reichel wrote:
From: Sebastian Reichel
nvmem_cell_write's buf argument uses different types based on
the configuration of CONFIG_NVMEM. The function prototype for
enabled NVMEM uses 'void *' type, but the s
On Mon, Sep 9, 2019 at 3:45 PM Sebastian Reichel wrote:
>
> From: Sebastian Reichel
>
> nvmem_cell_write's buf argument uses different types based on
> the configuration of CONFIG_NVMEM. The function prototype for
> enabled NVMEM uses 'void *' type, but the static dummy function
> for disabled NV
On 9/9/19 1:18 PM, Sebastian Reichel wrote:
Hi,
On Mon, Sep 09, 2019 at 12:26:06PM +0300, Nandor Han wrote:
On 9/8/19 3:10 PM, Sebastian Reichel wrote:
From: Sebastian Reichel
nvmem_cell_write's buf argument uses different types based on
the configuration of CONFIG_NVMEM. The function protot
Hi,
On Mon, Sep 09, 2019 at 12:26:06PM +0300, Nandor Han wrote:
> On 9/8/19 3:10 PM, Sebastian Reichel wrote:
> > From: Sebastian Reichel
> >
> > nvmem_cell_write's buf argument uses different types based on
> > the configuration of CONFIG_NVMEM. The function prototype for
> > enabled NVMEM uses
On 9/8/19 3:10 PM, Sebastian Reichel wrote:
From: Sebastian Reichel
nvmem_cell_write's buf argument uses different types based on
the configuration of CONFIG_NVMEM. The function prototype for
enabled NVMEM uses 'void *' type, but the static dummy function
for disabled NVMEM uses 'const char *'
From: Sebastian Reichel
nvmem_cell_write's buf argument uses different types based on
the configuration of CONFIG_NVMEM. The function prototype for
enabled NVMEM uses 'void *' type, but the static dummy function
for disabled NVMEM uses 'const char *' instead. Fix the different
behaviour by always
6 matches
Mail list logo