From: Rob Herring <robh@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] of: unittest: new node lifecycle tests
Date: Fri, 17 Feb 2023 15:44:02 -0600 [thread overview]
Message-ID: <20230217214402.GA1611091-robh@kernel.org> (raw)
In-Reply-To: <20230213185702.395776-1-frowand.list@gmail.com>
On Mon, Feb 13, 2023 at 12:56:55PM -0600, Frank Rowand wrote:
> Create new devicetree node lifecycle tests.
>
> The tests introduce use of EXPECT_NOT messages, similar to EXPECT
> messages. This requires updating scripts/dtc/of_unittest_expect
> to process EXPECT_NOT messages.
>
> The new tests revealed an issue in printk formatting when using
> format "%pOF" on a node with a reference count of zero. A patch
> is included to the fix the caller which revealed the issue.
>
> Update kconfig unittest help to further explain that unittests
> should only be enabled for developer kernels. Also add info
> about using scripts/dtc/of_unittest_expect to process the output
> of unittests.
>
> Add an additional consistency check to of_node_release(), which
> is the function that potentially frees node related memory when
> the node's reference count is decremented to zero.
>
> Add docbook documentation to the devicetree node creation functions
> about caller responsibility to call of_node_put() and how the
> memory free process works.
>
> Frank Rowand (7):
> of: prepare to add processing of EXPECT_NOT to of_unittest_expect
> of: add processing of EXPECT_NOT to of_unittest_expect
> of: update kconfig unittest help
> of: unittest: add node lifecycle tests
> of: do not use "%pOF" printk format on node with refcount of zero
> of: add consistency check to of_node_release()
> of: dynamic: add lifecycle docbook info to node creation functions
Series applied.
Rob
prev parent reply other threads:[~2023-02-17 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 18:56 [PATCH 0/7] of: unittest: new node lifecycle tests Frank Rowand
2023-02-13 18:56 ` [PATCH 1/7] of: prepare to add processing of EXPECT_NOT to of_unittest_expect Frank Rowand
2023-02-13 18:56 ` [PATCH 2/7] of: " Frank Rowand
2023-02-13 18:56 ` [PATCH 3/7] of: update kconfig unittest help Frank Rowand
2023-02-13 18:56 ` [PATCH 4/7] of: unittest: add node lifecycle tests Frank Rowand
2023-02-26 0:07 ` Guenter Roeck
2023-02-26 19:50 ` Frank Rowand
2023-02-26 21:42 ` Frank Rowand
2023-02-13 18:57 ` [PATCH 5/7] of: do not use "%pOF" printk format on node with refcount of zero Frank Rowand
2023-02-13 19:23 ` Frank Rowand
2023-02-13 19:27 ` Frank Rowand
2023-02-13 18:57 ` [PATCH 6/7] of: add consistency check to of_node_release() Frank Rowand
2023-02-13 18:57 ` [PATCH 7/7] of: dynamic: add lifecycle docbook info to node creation functions Frank Rowand
2023-02-17 21:44 ` Rob Herring [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=20230217214402.GA1611091-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.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).