[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c9819833-5c51-070b-ca77-ce273aa46fcf@gmail.com>
Date: Mon, 2 May 2022 13:44:19 -0500
From: Frank Rowand <frowand.list@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Slawomir Stepien <slawomir.stepien@...ia.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Slawomir Stepien <sst@...zta.fm>,
Jan Kiszka <jan.kiszka@...mens.com>,
Geert Uytterhoeven <geert+renesas@...der.be>
Subject: Re: [PATCH 1/3] of: overlay: add entry to of_overlay_action_name[]
On 5/2/22 13:29, Rob Herring wrote:
> On Mon, May 2, 2022 at 1:17 PM Frank Rowand <frowand.list@...il.com> wrote:
>>
>> On 5/2/22 12:00, Rob Herring wrote:
>>> On Sat, Apr 30, 2022 at 07:05:41PM -0500, frowand.list@...il.com wrote:
>>>> From: Frank Rowand <frank.rowand@...y.com>
>>>>
>>>> The values of enum of_overlay_notify_action are used to index into
>>>> array of_overlay_action_name. Add an entry to of_overlay_action_name
>>>> for the value recently added to of_overlay_notify_action.
>>>>
>>>> Array of_overlay_action_name[] is moved into include/linux/of.h
>>>> adjacent to enum of_overlay_notify_action to make the connection
>>>> between the two more obvious if either is modified in the future.
>>>>
>>>> The only use of of_overlay_action_name is for error reporting in
>>>> overlay_notify(). All callers of overlay_notify() report the same
>>>> error, but with fewer details. Remove the redundant error reports
>>>> in the callers.
>>>>
>>>> Fixes: 067c098766c6 ("of: overlay: rework overlay apply and remove kfree()s")
>>>> Reported-by: Dan Carpenter <dan.carpenter@...cle.com>
>>>> Signed-off-by: Frank Rowand <frank.rowand@...y.com>
>>>> ---
>>>> drivers/of/overlay.c | 27 +++++----------------------
>>>> include/linux/of.h | 13 +++++++++++++
>>>> 2 files changed, 18 insertions(+), 22 deletions(-)
>>>
>>> This isn't applying for me.
>>
>> Weird, patch can apply it, but 'git am' does not work. I see that when
>> I try that on your dt/next branch.
>>
>> The problem seems to be that I did not create the series on top of
>> dt/next: 5f756a2eaa44 of: overlay: do not break notify on NOTIFY_{OK|STOP}.
>
> It should be more than just that. It was also not any base I have in
> my tree, so 'git am' wouldn't try a 3-way merge either.
That was the only thing patch mentioned when it applied successfully,
a little bit of fuzz around the few lines in that patch. I thought
it a little weird that 'git am' didn't handle that, but it was easy
enough to rebase instead of debugging git.
>
>> I have rebased the series on top of that patch and am sending v2.
>
> Thanks.
I just now tried the v2 series emails on top of your dt/next and 'git am'
is happy with it.
>
> Rob
Powered by blists - more mailing lists