devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.17, part 1
Date: Mon, 25 Aug 2025 15:35:21 -0500	[thread overview]
Message-ID: <20250825203521.GA399593-robh@kernel.org> (raw)

Linus,

Please pull DT fixes for 6.17.

Rob


The following changes since commit 0121898ec05fa4c1f566fc05c7e8b3caf0998f97:

  dt-bindings: Correct indentation and style in DTS example (2025-07-28 19:56:29 -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-6.17-1

for you to fetch changes up to 80af3745ca465c6c47e833c1902004a7fa944f37:

  of: dynamic: Fix use after free in of_changeset_add_prop_helper() (2025-08-22 16:21:35 -0500)

----------------------------------------------------------------
Devicetree fixes for v6.17, part 1:

- Fix a memory leak for of_pci_add_properties() failure case. Then fix
  the introduced UAF.

- Add missing IORESOURCE_MEM flag on of_reserved_mem_region_to_resource()

- Add already in use vendor prefix "eswin"

- Clarify "of of" comment in of_match_device(). After many years of
  drive-by patches dropping the 2nd "of" (which referred to
  OpenFirmware), a correct patch finally arrived.

----------------------------------------------------------------
Bagas Sanjaya (1):
      of: Clarify OF device context in of_match_device() comment

Dan Carpenter (1):
      of: dynamic: Fix use after free in of_changeset_add_prop_helper()

Lizhi Hou (1):
      of: dynamic: Fix memleak when of_pci_add_properties() failed

Pritesh Patel (1):
      dt-bindings: vendor-prefixes: add eswin

Rob Herring (Arm) (1):
      of: reserved_mem: Add missing IORESOURCE_MEM flag on resources

 Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
 drivers/of/device.c                                    | 4 ++--
 drivers/of/dynamic.c                                   | 9 +++++++--
 drivers/of/of_reserved_mem.c                           | 1 +
 4 files changed, 12 insertions(+), 4 deletions(-)

             reply	other threads:[~2025-08-25 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 20:35 Rob Herring [this message]
2025-08-26  2:02 ` [GIT PULL] Devicetree fixes for v6.17, 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=20250825203521.GA399593-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 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).