From: Rob Herring <robh@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Petr Mladek <pmladek@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] dt: changeset fixes and cleanups
Date: Tue, 01 Aug 2023 15:54:43 -0600 [thread overview]
Message-ID: <20230801-dt-changeset-fixes-v1-0-b5203e3fc22f@kernel.org> (raw)
Geert's locking fix[1] prompted my closer look at
__of_changeset_entry_apply() and related functions. The result is a
couple of fixes I found and some refactoring that unifies the "old API"
and the changeset API.
[1] https://lore.kernel.org/all/c593d8389352c574b5be69d4ca4810da13326a50.1690533838.git.geert+renesas@glider.be/
Signed-off-by: Rob Herring <robh@kernel.org>
---
Rob Herring (5):
of: unittest: Fix EXPECT for parse_phandle_with_args_map() test
of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock
of: dynamic: Fix race in getting old property when updating property
of: dynamic: Move dead property list check into property add/update functions
of: Refactor node and property manipulation function locking
drivers/of/base.c | 86 ++++++++++++++++------------
drivers/of/dynamic.c | 153 +++++++++++---------------------------------------
drivers/of/unittest.c | 4 +-
3 files changed, 87 insertions(+), 156 deletions(-)
---
base-commit: e251a4e28a27884e8bfb7fccbf53b24736f3ef87
change-id: 20230801-dt-changeset-fixes-b76b88fecc43
Best regards,
--
Rob Herring <robh@kernel.org>
next reply other threads:[~2023-08-01 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 21:54 Rob Herring [this message]
2023-08-01 21:54 ` [PATCH 1/5] of: unittest: Fix EXPECT for parse_phandle_with_args_map() test Rob Herring
2023-08-01 21:54 ` [PATCH 2/5] of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock Rob Herring
2023-08-02 2:49 ` kernel test robot
2023-08-02 3:28 ` Andy Shevchenko
2023-08-02 3:35 ` Andy Shevchenko
2023-08-02 21:33 ` Rob Herring
2023-08-03 17:36 ` Rob Herring
2023-08-04 18:55 ` Petr Mladek
2023-08-04 20:31 ` Rob Herring
2023-08-01 21:54 ` [PATCH 3/5] of: dynamic: Fix race in getting old property when updating property Rob Herring
2023-08-01 21:54 ` [PATCH 4/5] of: dynamic: Move dead property list check into property add/update functions Rob Herring
2023-08-02 15:12 ` Andy Shevchenko
2023-08-03 20:42 ` Rob Herring
2023-08-01 21:54 ` [PATCH 5/5] of: Refactor node and property manipulation function locking Rob Herring
2023-08-02 15:14 ` Andy Shevchenko
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=20230801-dt-changeset-fixes-v1-0-b5203e3fc22f@kernel.org \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).