From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v6.13, part 1
Date: Sun, 22 Dec 2024 09:08:22 -0600 [thread overview]
Message-ID: <20241222150822.GA1972679-robh@kernel.org> (raw)
Linus,
Please pull DT fixes for 6.13-rc.
Rob
The following changes since commit 28b513b5a683cf1e7125ba54ffe7ecb206ef4984:
Merge branch 'dt/linus' into dt/next (2024-11-15 14:03:59 -0600)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-6.13-1
for you to fetch changes up to 8600058ba28a7b07660ddcd150372d72fb3bc895:
of: Add coreboot firmware to excluded default cells list (2024-12-20 15:39:22 -0600)
----------------------------------------------------------------
Devicetree fixes for 6.13, part 1:
- Disable #address-cells/#size-cells warning on coreboot (Chromebooks)
platforms
- Add missing root #address-cells/#size-cells in default empty DT
- Fix uninitialized variable in of_irq_parse_one()
- Fix interrupt-map cell length check in of_irq_parse_imap_parent()
- Fix refcount handling in __of_get_dma_parent()
- Fix error path in of_parse_phandle_with_args_map()
- Fix dma-ranges handling with flags cells
- Drop explicit fw_devlink handling of 'interrupt-parent'
- Fix "compression" typo in fixed-partitions binding
- Unify "fsl,liodn" property type definitions
----------------------------------------------------------------
Andrea della Porta (2):
of/unittest: Add empty dma-ranges address translation tests
of: address: Preserve the flags portion on 1:1 dma-ranges mapping
Herve Codina (2):
of: Add #address-cells/#size-cells in the device-tree root empty node
of: Fix error path in of_parse_phandle_with_args_map()
Rob Herring (Arm) (3):
dt-bindings: Unify "fsl,liodn" type definitions
dt-bindings: mtd: fixed-partitions: Fix "compression" typo
of: Add coreboot firmware to excluded default cells list
Samuel Holland (1):
of: property: fw_devlink: Do not use interrupt-parent directly
Zijun Hu (3):
of: Fix refcount leakage for OF node returned by __of_get_dma_parent()
of/irq: Fix interrupt-map cell length check in of_irq_parse_imap_parent()
of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one()
.../devicetree/bindings/crypto/fsl,sec-v4.0.yaml | 10 +++---
.../bindings/mtd/partitions/fixed-partitions.yaml | 2 +-
.../bindings/soc/fsl/fsl,qman-portal.yaml | 2 ++
drivers/of/address.c | 5 +--
drivers/of/base.c | 18 ++++++----
drivers/of/empty_root.dts | 9 ++++-
drivers/of/irq.c | 2 ++
drivers/of/property.c | 2 --
drivers/of/unittest-data/tests-address.dtsi | 2 ++
drivers/of/unittest.c | 39 ++++++++++++++++++++++
10 files changed, 75 insertions(+), 16 deletions(-)
next reply other threads:[~2024-12-22 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 15:08 Rob Herring [this message]
2024-12-22 16:54 ` [GIT PULL] Devicetree fixes for v6.13, part 1 pr-tracker-bot
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=20241222150822.GA1972679-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.com \
--cc=torvalds@linux-foundation.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 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.