From: Frank Rowand <frowand.list@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] of: overlay: Miscellaneous improvements
Date: Mon, 18 Jul 2022 18:42:52 -0500 [thread overview]
Message-ID: <d9f2ec3f-d531-80ef-d9cc-0926893d892f@gmail.com> (raw)
In-Reply-To: <cover.1657893306.git.geert+renesas@glider.be>
On 7/15/22 09:03, Geert Uytterhoeven wrote:
> Hi,
>
> While performing the long-overdue rebase of my topic/overlays branch[1]
> on top of the overlay rework in v5.19-rc1, I identified a few areas for
> improvement in the upstream code.
>
> Thanks for your comments!
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/overlays
>
> Geert Uytterhoeven (2):
> of: overlay: Move devicetree_corrupt() check up
> of: overlay: Simplify of_overlay_fdt_apply() tail
>
> drivers/of/overlay.c | 20 +++++++-------------
> 1 file changed, 7 insertions(+), 13 deletions(-)
>
The patches look good, based on a visual inspection. I'll build the kernel
and test the patches tomorrow morning.
-Frank
next prev parent reply other threads:[~2022-07-18 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 14:03 [PATCH 0/2] of: overlay: Miscellaneous improvements Geert Uytterhoeven
2022-07-15 14:03 ` [PATCH 1/2] of: overlay: Move devicetree_corrupt() check up Geert Uytterhoeven
2022-07-19 21:55 ` Rob Herring
2022-07-15 14:03 ` [PATCH 2/2] of: overlay: Simplify of_overlay_fdt_apply() tail Geert Uytterhoeven
2022-07-19 21:55 ` Rob Herring
2022-07-18 23:42 ` Frank Rowand [this message]
2022-07-19 18:37 ` [PATCH 0/2] of: overlay: Miscellaneous improvements Frank Rowand
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=d9f2ec3f-d531-80ef-d9cc-0926893d892f@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--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).