lkml.org 
[lkml]   [2020]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v4 0/1] nvmem: Add support for write-only instances, and clean-up
Date
Hello all,

Previous version: https://lkml.org/lkml/2020/3/9/731

Changed since previous version:

- Hopefully fixed memory leak fully. I set CONFIG_DEBUG_KMEMLEAK and
according to the leak detector, it is no longer leaking. I believe the
leak was when setting the device name. I could not find out how to
free that in the required context. But I avoided it by moving the
groups above setting the name.

If you believe there is still a leak, please be specific about what
you think it is. I have been reading up this week about the driver
interfaces and trying to figure it out, but I have had trouble finding
good reading material.

- I squashed the two patches together as advised by Srinivas.

- Changed from -EPERM to -EINVAL for invalid configuration.

Nicholas Johnson (1):
nvmem: Add support for write-only instances

drivers/nvmem/core.c | 9 ++++--
drivers/nvmem/nvmem-sysfs.c | 56 +++++++++++++++++++++++++++++++------
2 files changed, 54 insertions(+), 11 deletions(-)

--
2.25.1

\
 
 \ /
  Last update: 2020-03-17 02:01    [W:0.071 / U:0.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site