From: Puneet Saxena <puneets@nvidia.com>
To: robh+dt@kernel.org, pantelis.antoniou@konsulko.com,
frowand.list@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: treding@nvidia.com, vdumpa@nvidia.com, snikam@nvidia.com,
jonathanh@nvidia.com, Puneet Saxena <puneets@nvidia.com>
Subject: [PATCH] ignore disabled memory-region nodes
Date: Wed, 22 May 2019 16:17:10 +0530 [thread overview]
Message-ID: <1558522031-549-1-git-send-email-puneets@nvidia.com> (raw)
While parsing "memory-region" node lists if a node is
"disabled", parsing halts. Therefore the nodes whose
"status" is "okay" or "ok" are not parsed.
The change ignores disabled nodes in the memory-region
nodes list and returns 0 to continue parsing next nodes.
---
v2:
* Fixed typo in commit message.
* Used of_device_is_available to check device is disabled/enabled.
Krishna Reddy (1):
of: reserved-memory: ignore disabled memory-region nodes
drivers/of/of_reserved_mem.c | 3 +++
1 file changed, 3 insertions(+)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Puneet Saxena <puneets@nvidia.com>
To: <robh+dt@kernel.org>, <pantelis.antoniou@konsulko.com>,
<frowand.list@gmail.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <treding@nvidia.com>, <vdumpa@nvidia.com>, <snikam@nvidia.com>,
<jonathanh@nvidia.com>, Puneet Saxena <puneets@nvidia.com>
Subject: [PATCH] ignore disabled memory-region nodes
Date: Wed, 22 May 2019 16:17:10 +0530 [thread overview]
Message-ID: <1558522031-549-1-git-send-email-puneets@nvidia.com> (raw)
While parsing "memory-region" node lists if a node is
"disabled", parsing halts. Therefore the nodes whose
"status" is "okay" or "ok" are not parsed.
The change ignores disabled nodes in the memory-region
nodes list and returns 0 to continue parsing next nodes.
---
v2:
* Fixed typo in commit message.
* Used of_device_is_available to check device is disabled/enabled.
Krishna Reddy (1):
of: reserved-memory: ignore disabled memory-region nodes
drivers/of/of_reserved_mem.c | 3 +++
1 file changed, 3 insertions(+)
--
2.7.4
next reply other threads:[~2019-05-22 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 10:47 Puneet Saxena [this message]
2019-05-22 10:47 ` [PATCH] ignore disabled memory-region nodes Puneet Saxena
2019-05-22 10:47 ` [PATCH V2] of: reserved-memory: " Puneet Saxena
2019-05-22 10:47 ` Puneet Saxena
2019-05-24 20:53 ` Rob Herring
2019-05-24 20:53 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2019-05-22 5:35 [PATCH] " Puneet Saxena
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=1558522031-549-1-git-send-email-puneets@nvidia.com \
--to=puneets@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=snikam@nvidia.com \
--cc=treding@nvidia.com \
--cc=vdumpa@nvidia.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 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.