From: Rob Herring <robh@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
kernel@axis.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: reserved-memory: Print allocation/reservation failures as error
Date: Tue, 28 Jun 2022 10:09:27 -0600 [thread overview]
Message-ID: <20220628160927.GA547820-robh@kernel.org> (raw)
In-Reply-To: <20220628113540.2790835-1-vincent.whitchurch@axis.com>
On Tue, 28 Jun 2022 13:35:40 +0200, Vincent Whitchurch wrote:
> If the allocation/reservation of reserved-memory fails, it is normally
> an error, so print it as an error so that it doesn't get hidden from the
> console due to the loglevel. Also make the allocation failure include
> the size just like the reservation failure.
>
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> drivers/of/fdt.c | 4 ++--
> drivers/of/of_reserved_mem.c | 3 ++-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-06-28 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 11:35 [PATCH] of: reserved-memory: Print allocation/reservation failures as error Vincent Whitchurch
2022-06-28 16:09 ` 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=20220628160927.GA547820-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vincent.whitchurch@axis.com \
/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).