[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <PSXP216MB0438DB7146E07670FCDC1A7280F60@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
Date: Tue, 17 Mar 2020 01:00:26 +0000
From: Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
Subject: [PATCH v4 0/1] nvmem: Add support for write-only instances, and
clean-up
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
Powered by blists - more mailing lists