From: Rob Herring <robh@kernel.org>
To: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Cc: devicetree@vger.kernel.org, linux-can@vger.kernel.org,
Lizhi Hou <lizhi.hou@amd.com>
Subject: Re: [PATCH] of: overlay: Fix of_overlay_fdt_apply prototype when !CONFIG_OF_OVERLAY
Date: Tue, 5 Sep 2023 13:02:15 -0500 [thread overview]
Message-ID: <169393693413.3669145.6896827224153747407.robh@kernel.org> (raw)
In-Reply-To: <20230904100002.7913-1-pisa@cmp.felk.cvut.cz>
On Mon, 04 Sep 2023 12:00:02 +0200, Pavel Pisa wrote:
> The of_overlay_fdt_apply has been changed but when CONFIG_OF_OVERLAY
> support is not configured then old stub prototype is declared
> by of.h header.
>
> Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
> ---
> include/linux/of.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2023-09-05 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:00 [PATCH] of: overlay: Fix of_overlay_fdt_apply prototype when !CONFIG_OF_OVERLAY Pavel Pisa
2023-09-04 11:07 ` Marc Kleine-Budde
2023-09-05 18:02 ` Rob Herring [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=169393693413.3669145.6896827224153747407.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=pisa@cmp.felk.cvut.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).