From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Subject: [PATCH v3 0/2] nvmem: Add support for write-only instances, and clean-up
Date: Mon, 9 Mar 2020 17:49:08 +0000 [thread overview]
Message-ID: <PSXP216MB0438614877E3559E155F12AF80FE0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM> (raw)
Hello all,
Previous version: https://lkml.org/lkml/2020/3/2/693
Changed since previous version:
- Fixed memory leak when returning from nvmem_register().
- The patch 2/3 from last time was applied by Srinivas, so dropping it:
https://lkml.org/lkml/2020/3/5/616
- I split the patches into two as I said I would.
- Mika Westerberg asked me to send patch 3/3 to him again after v5.7-rc1
is released, so drop it for now:
https://lore.kernel.org/lkml/20200306053455.GY2540@lahna.fi.intel.com/
- Removed comment from last return in nvmem_sysfs_get_groups() to avoid
confusion.
Nicholas Johnson (2):
nvmem: Allow nvmem_sysfs_get_groups() to return NULL as error
condition
nvmem: Add support for write-only instances
drivers/nvmem/core.c | 4 +++
drivers/nvmem/nvmem-sysfs.c | 56 +++++++++++++++++++++++++++++++------
2 files changed, 52 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2020-03-09 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:49 Nicholas Johnson [this message]
2020-03-09 17:49 ` [PATCH v3 1/2] nvmem: Allow nvmem_sysfs_get_groups() to return NULL as error condition Nicholas Johnson
2020-03-10 13:10 ` Srinivas Kandagatla
2020-03-09 17:50 ` [PATCH v3 2/2] nvmem: Add support for write-only instances Nicholas Johnson
2020-03-10 1:10 ` Nicholas Johnson
2020-03-10 2:45 ` Nicholas Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PSXP216MB0438614877E3559E155F12AF80FE0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.