From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Saravana Kannan <saravanak@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v7.3, part 2
Date: Thu, 1 Oct 2026 14:35:46 -0500 [thread overview]
Message-ID: <20261001193546.GA1670288-robh@kernel.org> (raw)
Linus,
Please pull a few more DT fixes for 7.3.
Rob
The following changes since commit 5bb01c657ff9fc807c2c592ca18af34c4fc3bc6f:
of: fix out-of-bounds read in of_alias_scan() stem parser (2026-08-27 09:36:05 -0500)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-7.3-2
for you to fetch changes up to 30724547b221e0e670ddfef140fc7d816b2aaec6:
of/irq: Fix remaining refcount leaks in of_irq_init() (2026-09-30 16:09:13 -0500)
----------------------------------------------------------------
Devicetree fixes for v7.3, part 2:
- Fix another case of refcount leaks in of_irq_init()
- Avoid refcount leak in coreboot node check
- Fix overlay handling of a root node target path
- Various error path fixes in the overlay code
----------------------------------------------------------------
Abdurrahman Hussain (4):
of/overlay: put property on deadprops only after changeset add succeeds
of/overlay: only treat a positive changeset id as registered
of/overlay: don't leak fragment references when changeset init fails
of/overlay: don't create "//" paths for fragments targeting the root
Wentao Liang (1):
of/irq: Fix remaining refcount leaks in of_irq_init()
Yuho Choi (1):
of: Put coreboot node after compatibility check
drivers/of/base.c | 10 +++++++++-
drivers/of/irq.c | 2 ++
drivers/of/overlay.c | 17 +++++++++++++----
3 files changed, 24 insertions(+), 5 deletions(-)
next reply other threads:[~2026-10-01 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 19:35 Rob Herring [this message]
2026-10-01 21:38 ` 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=20261001193546.GA1670288-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®