From: Danilo Krummrich <dakr@kernel.org>
To: Xu Yang <xu.yang_2@oss.nxp.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org,
robh@kernel.org, saravanak@kernel.org,
andriy.shevchenko@linux.intel.com,
bartosz.golaszewski@oss.qualcomm.com,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v6 0/2] device property: add test cases for fwnode_for_each_child_node()
Date: Tue, 21 Jul 2026 23:43:46 +0200 [thread overview]
Message-ID: <20260721214344.1787957-3-dakr@kernel.org> (raw)
In-Reply-To: <20260721105448.2109894-1-xu.yang_2@oss.nxp.com>
On Tue, 21 Jul 2026 18:54:46 +0800, Xu Yang wrote:
> [PATCH v6 0/2] device property: add test cases for fwnode_for_each_child_node()
Applied, thanks!
Branch: driver-core-testing
Tree: git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
[1/2] of: kobj: export of_node_ktype for use by modules
commit: 08bc14983723
[ Add empty line before the kunit include. - Danilo ]
[2/2] device property: add test cases for fwnode_for_each_child_node()
commit: 0e6f8ccd4618
The patches will appear in the next linux-next integration (typically within 24
hours on weekdays).
The patches are in the driver-core-testing branch and will be promoted to
driver-core-next after validation.
prev parent reply other threads:[~2026-07-21 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 10:54 [PATCH v6 0/2] device property: add test cases for fwnode_for_each_child_node() Xu Yang
2026-07-21 10:54 ` [PATCH v6 1/2] of: kobj: export of_node_ktype for use by modules Xu Yang
2026-07-21 11:03 ` sashiko-bot
2026-07-21 11:16 ` Andy Shevchenko
2026-07-21 11:18 ` Andy Shevchenko
2026-07-21 14:29 ` Xu Yang
2026-07-21 13:37 ` Rob Herring
2026-07-21 10:54 ` [PATCH v6 2/2] device property: add test cases for fwnode_for_each_child_node() Xu Yang
2026-07-21 11:08 ` sashiko-bot
2026-07-21 11:17 ` Andy Shevchenko
2026-07-21 11:15 ` [PATCH v6 0/2] " Andy Shevchenko
2026-07-21 14:28 ` Xu Yang
2026-07-21 21:43 ` Danilo Krummrich [this message]
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=20260721214344.1787957-3-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@kernel.org \
--cc=xu.yang_2@oss.nxp.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