From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Shun-yi Wang <shun-yi.wang@mediatek.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
jason-ch.chen@mediatek.com, yaya.chang@mediatek.com,
teddy.chen@mediatek.com, olivia.wen@mediatek.com
Subject: Re: [PATCH 0/1] Support multiple reserved memory regions
Date: Wed, 10 Jul 2024 09:54:22 -0600 [thread overview]
Message-ID: <Zo6urhrP/Wl57sUp@p14s> (raw)
In-Reply-To: <20240703115308.17436-1-shun-yi.wang@mediatek.com>
Good morning,
On Wed, Jul 03, 2024 at 07:53:07PM +0800, Shun-yi Wang wrote:
> From: "shun-yi.wang" <shun-yi.wang@mediatek.com>
>
> Besides the reserved memory region for SCP, there are additional
> reserved memory regions for specific hardware use.
> Currently, only a single memory region is supported.
> Modifications are made to support multiple memory regions.
>
This is the changelog that should be in the patch. Usually there is no need for
a cover letter when there is a single patch in the set.
> shun-yi.wang (1):
> remoteproc: mediatek: support multiple reserved memory
>
> drivers/remoteproc/mtk_scp.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> --
> 2.18.0
>
prev parent reply other threads:[~2024-07-10 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 11:53 [PATCH 0/1] Support multiple reserved memory regions Shun-yi Wang
2024-07-03 11:53 ` [PATCH 1/1] remoteproc: mediatek: " Shun-yi Wang
2024-07-10 15:56 ` Mathieu Poirier
2024-07-12 8:21 ` AngeloGioacchino Del Regno
2024-07-10 15:54 ` Mathieu Poirier [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=Zo6urhrP/Wl57sUp@p14s \
--to=mathieu.poirier@linaro.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jason-ch.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=olivia.wen@mediatek.com \
--cc=shun-yi.wang@mediatek.com \
--cc=teddy.chen@mediatek.com \
--cc=yaya.chang@mediatek.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 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.