From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: 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>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] of: Refactor node and property manipulation function locking
Date: Wed, 2 Aug 2023 18:14:51 +0300 [thread overview]
Message-ID: <ZMpy6x+GBKKIv1VP@smile.fi.intel.com> (raw)
In-Reply-To: <20230801-dt-changeset-fixes-v1-5-b5203e3fc22f@kernel.org>
On Tue, Aug 01, 2023 at 03:54:48PM -0600, Rob Herring wrote:
> All callers of __of_{add,remove,update}_property() and
> __of_{attach,detach}_node() wrap the call with the devtree_lock
> spinlock. Let's move the spinlock into the functions. This allows moving
> the sysfs update functions into those functions as well.
...
> +out:
out_unlock: ?
> + raw_spin_unlock_irqrestore(&devtree_lock, flags);
> + if (!rc)
> + __of_add_property_sysfs(np, prop);
> +
> + return rc;
Why not
if (rc)
return rc;
__of_add_property_sysfs(np, prop);
return 0;
?
...
> +out:
> + raw_spin_unlock_irqrestore(&devtree_lock, flags);
> + if (!rc)
> + __of_remove_property_sysfs(np, prop);
> + return rc;
As per above.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-08-02 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 21:54 [PATCH 0/5] dt: changeset fixes and cleanups Rob Herring
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 [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=ZMpy6x+GBKKIv1VP@smile.fi.intel.com \
--to=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=robh@kernel.org \
--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