From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "Ben Dooks (Codethink)" <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
Ohad Ben-Cohen <ohad@wizery.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: fix argument 2 of rproc_mem_entry_init
Date: Fri, 8 Nov 2019 17:21:08 -0800 [thread overview]
Message-ID: <20191109012105.GD5662@tuxbook-pro> (raw)
In-Reply-To: <20191017115952.13935-1-ben.dooks@codethink.co.uk>
On Thu 17 Oct 04:59 PDT 2019, Ben Dooks (Codethink) wrote:
> The rproc_mem_entry_init() call takes a pointer to a vm
> as the second argument. The code is currently using a
> plain 0 as "NULL". Change to using NULL to fix the
> following sparse warnings:
>
> drivers/remoteproc/remoteproc_core.c:339:49: warning: Using plain integer as NULL pointer
> drivers/remoteproc/remoteproc_core.c:916:46: warning: Using plain integer as NULL pointer
>
Applied, thanks
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
> Cc: Ohad Ben-Cohen <ohad@wizery.com>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: linux-remoteproc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/remoteproc/remoteproc_core.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index 3c5fbbbfb0f1..943af836fa0f 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -336,7 +336,8 @@ int rproc_alloc_vring(struct rproc_vdev *rvdev, int i)
> return -ENOMEM;
> } else {
> /* Register carveout in in list */
> - mem = rproc_mem_entry_init(dev, 0, 0, size, rsc->vring[i].da,
> + mem = rproc_mem_entry_init(dev, NULL, 0,
> + size, rsc->vring[i].da,
> rproc_alloc_carveout,
> rproc_release_carveout,
> "vdev%dvring%d",
> @@ -913,7 +914,7 @@ static int rproc_handle_carveout(struct rproc *rproc,
> }
>
> /* Register carveout in in list */
> - carveout = rproc_mem_entry_init(dev, 0, 0, rsc->len, rsc->da,
> + carveout = rproc_mem_entry_init(dev, NULL, 0, rsc->len, rsc->da,
> rproc_alloc_carveout,
> rproc_release_carveout, rsc->name);
> if (!carveout) {
> --
> 2.23.0
>
prev parent reply other threads:[~2019-11-09 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 11:59 [PATCH] remoteproc: fix argument 2 of rproc_mem_entry_init Ben Dooks (Codethink)
2019-11-09 1:21 ` Bjorn Andersson [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=20191109012105.GD5662@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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