From: Michael Auchter <michael.auchter@ni.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: saravanak@google.com, robh+dt@kernel.org, frowand.list@gmail.com,
gregkh@linuxfoundation.org, rafael@kernel.org,
Michael Auchter <michael.auchter@ni.com>
Subject: [RFC PATCH 3/3] of: dynamic: add device links barrier before detach
Date: Wed, 14 Oct 2020 14:36:15 -0500 [thread overview]
Message-ID: <20201014193615.1045792-4-michael.auchter@ni.com> (raw)
In-Reply-To: <20201014193615.1045792-1-michael.auchter@ni.com>
Signed-off-by: Michael Auchter <michael.auchter@ni.com>
---
drivers/of/dynamic.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c
index 7478bfc8d440..a4e2881524e9 100644
--- a/drivers/of/dynamic.c
+++ b/drivers/of/dynamic.c
@@ -14,6 +14,7 @@
#include <linux/slab.h>
#include <linux/string.h>
#include <linux/proc_fs.h>
+#include <linux/device.h>
#include "of_private.h"
@@ -688,6 +689,8 @@ void of_changeset_destroy(struct of_changeset *ocs)
{
struct of_changeset_entry *ce, *cen;
+ device_links_barrier();
+
list_for_each_entry_safe_reverse(ce, cen, &ocs->entries, node)
__of_changeset_entry_destroy(ce);
}
--
2.25.4
next prev parent reply other threads:[~2020-10-14 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 19:36 [RFC PATCH 0/3] Fix errors on DT overlay removal with devlinks Michael Auchter
2020-10-14 19:36 ` [RFC PATCH 1/3] of: unittest: add test of overlay " Michael Auchter
2020-10-14 19:36 ` [RFC PATCH 2/3] driver core: add device_links_barrier Michael Auchter
2020-10-14 19:36 ` Michael Auchter [this message]
2020-10-15 21:34 ` [RFC PATCH 0/3] Fix errors on DT overlay removal with devlinks Frank Rowand
2020-10-21 21:02 ` Frank Rowand
2020-10-26 19:10 ` Saravana Kannan
2020-10-28 16:25 ` Michael Auchter
2020-10-28 18:03 ` Saravana Kannan
2020-10-29 20:54 ` Frank Rowand
2020-10-29 21:13 ` Michael Auchter
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=20201014193615.1045792-4-michael.auchter@ni.com \
--to=michael.auchter@ni.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.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