From: Dave Jiang <dave.jiang@intel.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Oliver O'Halloran <oohall@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvdimm: Use of_property_present() and of_property_read_bool()
Date: Wed, 7 Aug 2024 11:28:45 -0700 [thread overview]
Message-ID: <1b045ed5-b661-4d59-b43e-8d25cb1235ec@intel.com> (raw)
In-Reply-To: <20240731191312.1710417-26-robh@kernel.org>
On 7/31/24 12:13 PM, Rob Herring (Arm) wrote:
> Use of_property_present() and of_property_read_bool() to test
> property presence and read boolean properties rather than
> of_(find|get)_property(). This is part of a larger effort to remove
> callers of of_find_property() and similar functions.
> of_(find|get)_property() leak the DT struct property and data pointers
> which is a problem for dynamically allocated nodes which may be freed.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/nvdimm/of_pmem.c | 2 +-
> drivers/nvmem/layouts.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvdimm/of_pmem.c b/drivers/nvdimm/of_pmem.c
> index 403384f25ce3..b4a1cf70e8b7 100644
> --- a/drivers/nvdimm/of_pmem.c
> +++ b/drivers/nvdimm/of_pmem.c
> @@ -47,7 +47,7 @@ static int of_pmem_region_probe(struct platform_device *pdev)
> }
> platform_set_drvdata(pdev, priv);
>
> - is_volatile = !!of_find_property(np, "volatile", NULL);
> + is_volatile = of_property_read_bool(np, "volatile");
> dev_dbg(&pdev->dev, "Registering %s regions from %pOF\n",
> is_volatile ? "volatile" : "non-volatile", np);
>
> diff --git a/drivers/nvmem/layouts.c b/drivers/nvmem/layouts.c
> index 77a4119efea8..65d39e19f6ec 100644
> --- a/drivers/nvmem/layouts.c
> +++ b/drivers/nvmem/layouts.c
> @@ -123,7 +123,7 @@ static int nvmem_layout_bus_populate(struct nvmem_device *nvmem,
> int ret;
>
> /* Make sure it has a compatible property */
> - if (!of_get_property(layout_dn, "compatible", NULL)) {
> + if (!of_property_present(layout_dn, "compatible")) {
> pr_debug("%s() - skipping %pOF, no compatible prop\n",
> __func__, layout_dn);
> return 0;
next prev parent reply other threads:[~2024-08-07 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 19:13 [PATCH] nvdimm: Use of_property_present() and of_property_read_bool() Rob Herring (Arm)
2024-08-07 18:28 ` Dave Jiang [this message]
2024-09-03 19:17 ` Rob Herring
2024-09-04 13:50 ` Ira Weiny
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=1b045ed5-b661-4d59-b43e-8d25cb1235ec@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=oohall@gmail.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vishal.l.verma@intel.com \
/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