From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] remoteproc: debug: fix va dump format in carveout list
Date: Thu, 6 Jun 2019 08:43:32 -0700 [thread overview]
Message-ID: <20190606154332.GB23094@builder> (raw)
In-Reply-To: <1559835519-8165-1-git-send-email-arnaud.pouliquen@st.com>
On Thu 06 Jun 08:38 PDT 2019, Arnaud Pouliquen wrote:
> Standardize dump presentation for va, dma and da dumps by adding
> "0x" prefix for virtual address.
>
> Fixes: 276ec9934231("remoteproc: replace "%p" with "%pK"")
>
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Applied
Thanks,
Bjorn
> ---
> drivers/remoteproc/remoteproc_debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/remoteproc_debugfs.c b/drivers/remoteproc/remoteproc_debugfs.c
> index 6da934b8dc4b..91d3a75f0b41 100644
> --- a/drivers/remoteproc/remoteproc_debugfs.c
> +++ b/drivers/remoteproc/remoteproc_debugfs.c
> @@ -298,7 +298,7 @@ static int rproc_carveouts_show(struct seq_file *seq, void *p)
> list_for_each_entry(carveout, &rproc->carveouts, node) {
> seq_puts(seq, "Carveout memory entry:\n");
> seq_printf(seq, "\tName: %s\n", carveout->name);
> - seq_printf(seq, "\tVirtual address: %pK\n", carveout->va);
> + seq_printf(seq, "\tVirtual address: 0x%pK\n", carveout->va);
> seq_printf(seq, "\tDMA address: %pad\n", &carveout->dma);
> seq_printf(seq, "\tDevice address: 0x%x\n", carveout->da);
> seq_printf(seq, "\tLength: 0x%x Bytes\n\n", carveout->len);
> --
> 2.7.4
>
prev parent reply other threads:[~2019-06-06 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 15:38 [PATCH] remoteproc: debug: fix va dump format in carveout list Arnaud Pouliquen
2019-06-06 15:43 ` 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=20190606154332.GB23094@builder \
--to=bjorn.andersson@linaro.org \
--cc=arnaud.pouliquen@st.com \
--cc=linux-arm-msm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).