From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Xu Yang <xu.yang_2@nxp.com>,
linux-acpi@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org, Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/3] device property: add test cases for fwnode_for_each_child_node()
Date: Sun, 19 Jul 2026 11:37:49 +0300 [thread overview]
Message-ID: <alyMt-ya5skHmhtx@ashevche-desk.local> (raw)
In-Reply-To: <DK1RFV9AABBD.KP0VPMWKFYWM@kernel.org>
On Sat, Jul 18, 2026 at 04:18:12PM +0200, Danilo Krummrich wrote:
> On Thu Jun 11, 2026 at 10:31 PM CEST, Andy Shevchenko wrote:
> >
> > Add test cases for fwnode_for_each_child_node() API.
> >
> > Test command:
> > $ ./tools/testing/kunit/kunit.py run property-entry
> >
> > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> This patch broke the build [1], hence I dropped it from the queue (but kept the
> first two patches of this series).
>
> of_node_init() can't be used from modules, either it needs EXPORT_SYMBOL_GPL()
> itself, or of_node_ktype needs to be exported for this kunit test to work.
Oh, thanks for pointing out.
> [1] https://lore.kernel.org/all/202607181651.RnUuV8n6-lkp@intel.com/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-19 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260611203537.1786399-1-andriy.shevchenko@linux.intel.com>
[not found] ` <20260611203537.1786399-4-andriy.shevchenko@linux.intel.com>
2026-07-18 14:18 ` [PATCH v4 3/3] device property: add test cases for fwnode_for_each_child_node() Danilo Krummrich
2026-07-19 8:37 ` Andy Shevchenko [this message]
2026-07-20 10:46 ` Xu Yang
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=alyMt-ya5skHmhtx@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=saravanak@kernel.org \
--cc=xu.yang_2@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