From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srini@kernel.org>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: fastrpc: Use of_reserved_mem_region_to_resource() for "memory-region"
Date: Wed, 16 Jul 2025 14:16:51 +0200 [thread overview]
Message-ID: <2025071645-unwieldy-chrome-8904@gregkh> (raw)
In-Reply-To: <acd5b3e3-5370-49a4-aad9-b1001aa0eb5a@kernel.org>
On Sat, Jul 12, 2025 at 07:27:42PM +0100, Srinivas Kandagatla wrote:
>
>
> On 7/3/25 7:34 PM, Rob Herring (Arm) wrote:
> > Use the newly added of_reserved_mem_region_to_resource() function to
> > handle "memory-region" properties.
> >
> > The error handling is a bit different. "memory-region" is optional, so
> > failed lookup is not an error. But then an error in
> > of_reserved_mem_lookup() is treated as an error. However, that
> > distinction is not really important. Either the region is available
> > and usable or it is not. So now, it is just
> > of_reserved_mem_region_to_resource() which is checked for an error.
> >
> > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> > ---
>
> Reviewed-by: Srinivas Kandagatla <srini@kernel.org>
>
>
> Greg, there are no more patches for fastrpc for this cycle, can you
> please pick this up via char-misc tree?
Will do, thanks.
greg k-h
prev parent reply other threads:[~2025-07-16 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 18:34 [PATCH] misc: fastrpc: Use of_reserved_mem_region_to_resource() for "memory-region" Rob Herring (Arm)
2025-07-03 19:45 ` Dmitry Baryshkov
2025-07-12 18:27 ` Srinivas Kandagatla
2025-07-16 12:16 ` Greg Kroah-Hartman [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=2025071645-unwieldy-chrome-8904@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.