[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a4aa779-f8b8-4178-8d65-b6aae9183fb7@kadam.mountain>
Date: Fri, 4 Aug 2023 19:05:20 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: oe-kbuild@...ts.linux.dev,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
lkp@...el.com, oe-kbuild-all@...ts.linux.dev,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Robert Marko <robert.marko@...tura.hr>,
Luka Perkov <luka.perkov@...tura.hr>,
Michael Walle <michael@...le.cc>, linux-kernel@...r.kernel.org,
Randy Dunlap <rdunlap@...radead.org>,
Chen-Yu Tsai <wenst@...omium.org>,
Daniel Golle <daniel@...rotopia.org>,
Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH v7 5/7] nvmem: core: Rework layouts to become platform
devices
On Fri, Aug 04, 2023 at 05:46:25PM +0200, Miquel Raynal wrote:
> Actually of_nvmem_layout_get_container() already returns NULL if
> CONFIG_OF is not defined. This helper returns either a valid pointer of
> NULL. Where can it return an error pointer?
This is from linux-next.
include/linux/nvmem-consumer.h
256 static inline struct device_node *
257 of_nvmem_layout_get_container(struct nvmem_device *nvmem)
258 {
259 return ERR_PTR(-EOPNOTSUPP);
260 }
261 #endif /* CONFIG_NVMEM && CONFIG_OF */
regards,
dan carpenter
Powered by blists - more mailing lists