From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: "Nuno Sá" <noname.nuno@gmail.com>, "Nuno Sá" <nuno.sa@analog.com>,
devicetree@vger.kernel.org,
"Pantelis Antoniou" <pantelis.antoniou@konsulko.com>,
"Alan Tull" <atull@kernel.org>,
"Frank Rowand" <frowand.list@gmail.com>
Subject: Re: [PATCH] of: overlay: do not break notify on NOTIFY_OK
Date: Tue, 19 Apr 2022 10:20:53 -0500 [thread overview]
Message-ID: <c3e31c55-01c2-5784-1e97-5af083c1a0c1@gmail.com> (raw)
In-Reply-To: <CAL_JsqKjuOEdzB4SH6MB0bH58D5ys3RLhi=T8DhWQRuwMhbJOA@mail.gmail.com>
Hi Rob, Nuno,
On 4/19/22 09:48, Rob Herring wrote:
> On Tue, Apr 19, 2022 at 9:32 AM Frank Rowand <frowand.list@gmail.com> wrote:
>>
>> Hi Rob, Nuno,
>>
>> (adding cc: Alan)
>
> Alan is not active and Altera doesn't exist.
>
>> You just applied the patch at the root of this email thread.
>
> Well, no one had commented further after 2 weeks and the patch looked
> like a move in the right direction as-is.
Agreed.
>
>> Please either revert it and accept the alternate that Nuno
>> suggests below, or if you do not want to follow that path,
>> then Nuno please add a follow on patch that does what you suggest
>> below.
>
> Okay, Dropped as it's not pushed out.
Thanks. I thought that might be possible...
Nuno, can you please create the alternate patch you suggested? It
also fixes the additional problem that you noted.
-Frank
>
> Rob
next prev parent reply other threads:[~2022-04-19 15: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á
2022-04-19 14:32 ` Frank Rowand
2022-04-19 14:48 ` Rob Herring
2022-04-19 15:20 ` Frank Rowand [this message]
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=c3e31c55-01c2-5784-1e97-5af083c1a0c1@gmail.com \
--to=frowand.list@gmail.com \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=noname.nuno@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).