From: "Rob Herring (Arm)" <robh@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Saravana Kannan <saravanak@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH 0/7] of: Constify DT structs
Date: Thu, 10 Oct 2024 11:27:13 -0500 [thread overview]
Message-ID: <20241010-dt-const-v1-0-87a51f558425@kernel.org> (raw)
This series constifies many usages of DT structs in the DT core code.
Many uses of struct device_node where the node refcount is not
changed can be const. Most uses of struct property can also be const.
The first 2 patches are dependencies. The functions called by the
DT core where the fwnode_handle needs to be const to make the containing
device_node const.
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
Rob Herring (Arm) (7):
PCI: Constify pci_register_io_range() fwnode_handle
logic_pio: Constify fwnode_handle
of: Constify struct device_node function arguments
of: Constify struct property pointers
of: Constify of_changeset_entry function arguments
of: Constify safe_name() kobject arg
of/address: Constify of_busses[] array and pointers
drivers/of/address.c | 22 +++++++++++-----------
drivers/of/base.c | 20 ++++++++++----------
drivers/of/cpu.c | 2 +-
drivers/of/dynamic.c | 4 ++--
drivers/of/irq.c | 4 ++--
drivers/of/kobj.c | 8 ++++----
drivers/of/of_private.h | 12 ++++++------
drivers/of/overlay.c | 19 ++++++++++---------
drivers/of/property.c | 10 +++++-----
drivers/of/resolver.c | 12 ++++++------
drivers/pci/pci.c | 2 +-
include/linux/logic_pio.h | 6 +++---
include/linux/of.h | 28 ++++++++++++++--------------
include/linux/of_address.h | 6 +++---
include/linux/of_irq.h | 4 ++--
include/linux/pci.h | 2 +-
lib/logic_pio.c | 4 ++--
17 files changed, 83 insertions(+), 82 deletions(-)
---
base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
change-id: 20241010-dt-const-7ceef73df29c
Best regards,
--
Rob Herring (Arm) <robh@kernel.org>
next reply other threads:[~2024-10-10 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 16:27 Rob Herring (Arm) [this message]
2024-10-10 16:27 ` [PATCH 1/7] PCI: Constify pci_register_io_range() fwnode_handle Rob Herring (Arm)
2024-10-10 22:07 ` Bjorn Helgaas
2024-10-11 14:58 ` Krzysztof Kozlowski
2024-10-10 16:27 ` [PATCH 2/7] logic_pio: Constify fwnode_handle Rob Herring (Arm)
2024-10-11 14:59 ` Krzysztof Kozlowski
2024-10-11 15:08 ` Rob Herring
2024-10-10 16:27 ` [PATCH 3/7] of: Constify struct device_node function arguments Rob Herring (Arm)
2024-10-11 15:13 ` Krzysztof Kozlowski
2024-10-10 16:27 ` [PATCH 4/7] of: Constify struct property pointers Rob Herring (Arm)
2024-10-11 15:17 ` Krzysztof Kozlowski
2024-10-10 16:27 ` [PATCH 5/7] of: Constify of_changeset_entry function arguments Rob Herring (Arm)
2024-10-11 15:18 ` Krzysztof Kozlowski
2024-10-10 16:27 ` [PATCH 6/7] of: Constify safe_name() kobject arg Rob Herring (Arm)
2024-10-11 15:18 ` Krzysztof Kozlowski
2024-10-10 16:27 ` [PATCH 7/7] of/address: Constify of_busses[] array and pointers Rob Herring (Arm)
2024-10-11 15:20 ` [PATCH 0/7] of: Constify DT structs Krzysztof Kozlowski
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=20241010-dt-const-v1-0-87a51f558425@kernel.org \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).