From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v6.5, take 2
Date: Tue, 22 Aug 2023 12:43:28 -0500 [thread overview]
Message-ID: <20230822174328.GA385825-robh@kernel.org> (raw)
Linus,
Please pull a few more DT fixes for 6.5.
Rob
The following changes since commit ffc59c6414f9ffd52591786efe3e62e145563deb:
dt-bindings: serial: Remove obsolete nxp,lpc1850-uart.txt (2023-07-21 13:39:12 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-6.5-2
for you to fetch changes up to 7882541ca06d51a6c12d687827176c16d5e05f65:
of/platform: increase refcount of fwnode (2023-08-21 16:12:28 -0500)
----------------------------------------------------------------
Devicetree fixes for v6.5, part 2:
- Fix DT node refcount when creating platform devices
- Fix deadlock in changeset code due to printing with devtree_lock held
- Fix unittest EXPECT strings for parse_phandle_with_args_map() test
- Fix IMA kexec memblock freeing
----------------------------------------------------------------
Peng Fan (1):
of/platform: increase refcount of fwnode
Rik van Riel (1):
mm,ima,kexec,of: use memblock_free_late from ima_free_kexec_buffer
Rob Herring (2):
of: unittest: Fix EXPECT for parse_phandle_with_args_map() test
of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock
drivers/of/dynamic.c | 31 +++++++++----------------------
drivers/of/kexec.c | 3 ++-
drivers/of/platform.c | 4 ++--
drivers/of/unittest.c | 4 ++--
4 files changed, 15 insertions(+), 27 deletions(-)
next reply other threads:[~2023-08-22 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 17:43 Rob Herring [this message]
2023-08-22 18:21 ` [GIT PULL] Devicetree fixes for v6.5, take 2 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=20230822174328.GA385825-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.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 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.