mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Robert Marko" <robert.marko@sartura.hr>,
	"Luka Perkov" <luka.perkov@sartura.hr>,
	"Michael Walle" <michael@walle.cc>,
	linux-kernel@vger.kernel.org,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Chen-Yu Tsai" <wenst@chromium.org>,
	"Daniel Golle" <daniel@makrotopia.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"kernel test robot" <lkp@intel.com>,
	"Dan Carpenter" <dan.carpenter@linaro.org>
Subject: [PATCH v8 2/8] nvmem: core: Return NULL when no nvmem layout is found
Date: Mon,  7 Aug 2023 10:24:13 +0200	[thread overview]
Message-ID: <20230807082419.38780-3-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20230807082419.38780-1-miquel.raynal@bootlin.com>

Currently, of_nvmem_layout_get_container() returns NULL on error, or an
error pointer if either CONFIG_NVMEM or CONFIG_OF is turned off. We
should likely avoid this kind of mix for two reasons: to clarify the
intend and anyway fix the !CONFIG_OF which will likely always if we use
this helper somewhere else. Let's just return NULL when no layout is
found, we don't need an error value here.

Link: https://staticthinking.wordpress.com/2022/08/01/mixing-error-pointers-and-null/
Fixes: 266570f496b9 ("nvmem: core: introduce NVMEM layouts")
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Closes: https://lore.kernel.org/r/202308030002.DnSFOrMB-lkp@intel.com/
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

---

Backports to stable kernels is likely not needed as I believe the error
pointer will be discarded "magically" by the of/ code.
---
 include/linux/nvmem-consumer.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/nvmem-consumer.h b/include/linux/nvmem-consumer.h
index fa030d93b768..27373024856d 100644
--- a/include/linux/nvmem-consumer.h
+++ b/include/linux/nvmem-consumer.h
@@ -256,7 +256,7 @@ static inline struct nvmem_device *of_nvmem_device_get(struct device_node *np,
 static inline struct device_node *
 of_nvmem_layout_get_container(struct nvmem_device *nvmem)
 {
-	return ERR_PTR(-EOPNOTSUPP);
+	return NULL;
 }
 #endif /* CONFIG_NVMEM && CONFIG_OF */
 
-- 
2.34.1


  parent reply	other threads:[~2023-08-07  8:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  8:24 [PATCH v8 0/8] NVMEM cells in sysfs Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 1/8] nvmem: core: Create all cells before adding the nvmem device Miquel Raynal
2023-08-07  8:24 ` Miquel Raynal [this message]
2023-08-07  8:24 ` [PATCH v8 3/8] nvmem: core: Do not open-code existing functions Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 4/8] nvmem: core: Track the registered devices Miquel Raynal
2023-08-07  9:02   ` Greg Kroah-Hartman
2023-08-07 12:10     ` Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 5/8] nvmem: core: Notify when a new layout is registered Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 6/8] nvmem: core: Rework layouts to become platform devices Miquel Raynal
2023-08-07  9:05   ` Greg Kroah-Hartman
2023-08-07  9:33     ` Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 7/8] ABI: sysfs-nvmem-cells: Expose cells through sysfs Miquel Raynal
2023-08-07  8:24 ` [PATCH v8 8/8] nvmem: core: " Miquel Raynal
2023-08-07  8:57 ` [PATCH v8 0/8] NVMEM cells in sysfs Chen-Yu Tsai
2023-08-07  9:20   ` Miquel Raynal
2023-08-07 14:28     ` Miquel Raynal
2023-08-08  2:56       ` Chen-Yu Tsai
2023-08-08  6:29         ` Miquel Raynal

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=20230807082419.38780-3-miquel.raynal@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=dan.carpenter@linaro.org \
    --cc=daniel@makrotopia.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luka.perkov@sartura.hr \
    --cc=michael@walle.cc \
    --cc=rafal@milecki.pl \
    --cc=rdunlap@infradead.org \
    --cc=robert.marko@sartura.hr \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wenst@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®