From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
pantelis.antoniou@konsulko.com,
Slawomir Stepien <slawomir.stepien@nokia.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Slawomir Stepien <sst@poczta.fm>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Alan Tull <atull@kernel.org>, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 0/2] of: overlay: rework overlay apply and remove kfree()s
Date: Sun, 10 Apr 2022 23:10:48 -0500 [thread overview]
Message-ID: <a2679425-3486-2823-01f7-6b208d296564@gmail.com> (raw)
In-Reply-To: <20220410210833.441504-1-frowand.list@gmail.com>
adding cc: Jan Kiszka <jan.kiszka@siemens.com>
On 4/10/22 16:08, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Fix various kfree() issues related to of_overlay_apply().
>
> The fixes revealed inconsist variable names for the same variable
> across functions, resulting in difficulty understanding the code
> that was being modified. Doing both variable renaming and the
> fixes results in a hard to review patch, so split into two patches.
>
> The first patch in the series contains only variable renaming.
> The second patch contains the kfree() related fixes.
>
> Frank Rowand (2):
> of: overlay: rename variables to be consistent
> of: overlay: rework overlay apply and remove kfree()s
>
> Documentation/devicetree/overlay-notes.rst | 23 ++-
> drivers/of/overlay.c | 175 +++++++++++----------
> 2 files changed, 115 insertions(+), 83 deletions(-)
>
prev parent reply other threads:[~2022-04-11 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 21:08 [PATCH v2 0/2] of: overlay: rework overlay apply and remove kfree()s frowand.list
2022-04-10 21:08 ` [PATCH v2 1/2] of: overlay: rename variables to be consistent frowand.list
2022-04-11 4:10 ` Frank Rowand
2022-04-12 10:23 ` Slawomir Stepien
2022-04-10 21:08 ` [PATCH v2 2/2] of: overlay: rework overlay apply and remove kfree()s frowand.list
2022-04-10 21:49 ` Frank Rowand
2022-04-11 4:11 ` Frank Rowand
2022-04-12 10:23 ` Slawomir Stepien
2022-04-12 14:00 ` Rob Herring
2022-04-12 17:20 ` Frank Rowand
2022-04-19 0:02 ` Frank Rowand
2022-04-11 4:10 ` Frank Rowand [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=a2679425-3486-2823-01f7-6b208d296564@gmail.com \
--to=frowand.list@gmail.com \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=slawomir.stepien@nokia.com \
--cc=sst@poczta.fm \
/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).