From: Rob Herring <robh@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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 v2 5/6] of: dynamic: Move dead property list check into property add/update functions
Date: Thu, 17 Aug 2023 12:09:34 -0500 [thread overview]
Message-ID: <20230817170934.GA1495946-robh@kernel.org> (raw)
In-Reply-To: <ZNEPqwQ0H9srkxxq@smile.fi.intel.com>
On Mon, Aug 07, 2023 at 06:37:15PM +0300, Andy Shevchenko wrote:
> On Fri, Aug 04, 2023 at 04:41:55PM -0600, Rob Herring wrote:
> > The changeset code checks for a property in the deadprops list when
> > adding/updating a property, but of_add_property() and
> > of_update_property() do not. As the users of these functions are pretty
> > simple, they have not hit this scenario or else the property lists
> > would get corrupted.
>
> Suggested-by: ? :-)
Humm, by me? The change in behavior and point of this patch comes from
me. You've provided review comments which will get covered by a
Reviewed-by I presume.
>
> ...
>
> > +static void __of_remove_dead_property(struct device_node *np, struct property *prop)
> > +{
> > + struct property **next;
> > +
> > + /* If the property is in deadprops then it must be removed */
> > + for (next = &np->deadprops; *next; next = &(*next)->next) {
> > + if (*next != prop)
> > + continue;
> > +
> > + *next = prop->next;
> > + prop->next = NULL;
> > + break;
>
> Why not
>
> if (*next == prop) {
> *next = prop->next;
> prop->next = NULL;
> break;
> }
>
> which seems to me clearer?
Sure. I like the style I wrote, but whichever way ends the discussion is
fine for me.
Rob
next prev parent reply other threads:[~2023-08-17 17:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 22:41 [PATCH v2 0/6] dt: changeset fixes and cleanups Rob Herring
2023-08-04 22:41 ` [PATCH v2 1/6] of: unittest: Fix EXPECT for parse_phandle_with_args_map() test Rob Herring
2023-08-18 15:27 ` Geert Uytterhoeven
2023-08-04 22:41 ` [PATCH v2 2/6] of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock Rob Herring
2023-08-07 15:30 ` Andy Shevchenko
2023-08-18 15:36 ` Geert Uytterhoeven
2023-08-18 16:16 ` Rob Herring
2023-08-18 17:36 ` Geert Uytterhoeven
2023-08-18 18:13 ` Rob Herring
2023-08-04 22:41 ` [PATCH v2 3/6] of: dynamic: Refactor changeset action printing to common helpers Rob Herring
2023-08-04 22:41 ` [PATCH v2 4/6] of: dynamic: Fix race in getting old property when updating property Rob Herring
2023-08-04 22:41 ` [PATCH v2 5/6] of: dynamic: Move dead property list check into property add/update functions Rob Herring
2023-08-07 15:37 ` Andy Shevchenko
2023-08-17 17:09 ` Rob Herring [this message]
2023-08-17 17:15 ` Andy Shevchenko
2023-08-04 22:41 ` [PATCH v2 6/6] of: Refactor node and property manipulation function locking Rob Herring
2023-08-07 15:40 ` 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=20230817170934.GA1495946-robh@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).