From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Frank Rowand" <frowand.list@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH] of: overlay: do not break notify on NOTIFY_OK
Date: Tue, 05 Apr 2022 09:19:20 +0200 [thread overview]
Message-ID: <9bde64d0c05a37e72fabbeb39d8d2fe099526917.camel@gmail.com> (raw)
In-Reply-To: <01e77fbd-5c26-6b15-be1f-f962aa4190c6@gmail.com>
On Mon, 2022-04-04 at 13:10 -0500, Frank Rowand wrote:
> On 4/4/22 02:40, Nuno Sá wrote:
> > We should not break overlay notifications on NOTIFY_OK otherwise we
> > might
> > break on the first fragment. As NOTIFY_OK is not zero, we need to
> > account for that when looking for errors.
>
> It's been a long time since I've looked at notifiers, it will take me
> some time to
> review this.
>
> -Frank
>
> >
Yeah, it was also my first time looking at of dynamic code. But it just
didn't felt right to stop fragmment notifications if someone returns
NOTIFY_OK. In fact, I'm starting to think that even if someone wants to
NOTIFY_STOP on the current fragment, that should not mean we should not
send notifications for the remaining ones. So, maybe the right patch is
actually something like:
ret = blocking_notifier_call_chain()
if (notifier_to_errno(ret))
return notifier_to_errno(ret);
This would also be more in line (not totally identical) with
'__of_changeset_revert_notify()'.
- Nuno Sá
>
>
next prev parent reply other threads:[~2022-04-05 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 7:40 [PATCH] of: overlay: do not break notify on NOTIFY_OK Nuno Sá
2022-04-04 18:10 ` Frank Rowand
2022-04-05 7:19 ` Nuno Sá [this message]
2022-04-19 14:32 ` Frank Rowand
2022-04-19 14:48 ` Rob Herring
2022-04-19 15:20 ` Frank Rowand
2022-04-19 15:50 ` Sa, Nuno
2022-04-19 13:02 ` Rob Herring
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=9bde64d0c05a37e72fabbeb39d8d2fe099526917.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=nuno.sa@analog.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@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).