From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: oe-kbuild@lists.linux.dev,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
"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>
Subject: Re: [PATCH v7 5/7] nvmem: core: Rework layouts to become platform devices
Date: Fri, 4 Aug 2023 18:47:57 +0200 [thread overview]
Message-ID: <20230804184757.66bc6abe@xps-13> (raw)
In-Reply-To: <3a4aa779-f8b8-4178-8d65-b6aae9183fb7@kadam.mountain>
Hi Dan,
dan.carpenter@linaro.org wrote on Fri, 4 Aug 2023 19:05:20 +0300:
> 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.
Ah! Ok I missed that one, we don't need this double implementation, as
of_nvmem_layout_get_container just calls a function that already has a
static inline counterpart in the of.h header, which returns NULL. I'll
make the change, thanks for the pointer.
>
> 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
Thanks,
Miquèl
next prev parent reply other threads:[~2023-08-04 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:21 [PATCH v7 0/7] NVMEM cells in sysfs Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 1/7] nvmem: core: Create all cells before adding the nvmem device Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 2/7] nvmem: core: Do not open-code existing functions Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 3/7] nvmem: core: Track the registered devices Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 4/7] nvmem: core: Notify when a new layout is registered Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 5/7] nvmem: core: Rework layouts to become platform devices Miquel Raynal
2023-08-03 10:13 ` Dan Carpenter
2023-08-04 15:39 ` Miquel Raynal
2023-08-04 15:46 ` Miquel Raynal
2023-08-04 16:05 ` Dan Carpenter
2023-08-04 16:47 ` Miquel Raynal [this message]
2023-08-04 16:02 ` Dan Carpenter
2023-08-01 18:21 ` [PATCH v7 6/7] ABI: sysfs-nvmem-cells: Expose cells through sysfs Miquel Raynal
2023-08-05 14:50 ` Daniel Golle
2023-08-07 7:20 ` Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 7/7] nvmem: core: " 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=20230804184757.66bc6abe@xps-13 \
--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=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--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