All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Loic Pallardy <loic.pallardy@st.com>
Cc: ohad@wizery.com, linux-remoteproc@vger.kernel.org,
	linux-kernel@vger.kernel.org, arnaud.pouliquen@st.com,
	benjamin.gaignard@linaro.org
Subject: Re: [PATCH v2 0/2] remoteproc: increase debug capabilities
Date: Mon, 6 Nov 2017 22:03:31 -0800	[thread overview]
Message-ID: <20171107060331.GA22677@builder> (raw)
In-Reply-To: <1509988196-24377-1-git-send-email-loic.pallardy@st.com>

On Mon 06 Nov 09:09 PST 2017, Loic Pallardy wrote:

> This series increases remoteproc debug capabilities by adding:
> - associated resource table dump feature
> - registered carveouts list dump feature
> 

Looks good, patches applied to rproc-next

Regards,
Bjorn

> ---
> Changes from V1:
> - Fix 0-DAY reported issues on open functions prototype
> - Rebase on Linux 4.14-rc8
> 
> Loic Pallardy (2):
>   remoteproc: debug: add resource table dump feature
>   remoteproc: debug: add carveouts list dump feature
> 
>  drivers/remoteproc/remoteproc_debugfs.c | 130 ++++++++++++++++++++++++++++++++
>  1 file changed, 130 insertions(+)
> 
> -- 
> 1.9.1
> 

  parent reply	other threads:[~2017-11-07  6:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 17:09 [PATCH v2 0/2] remoteproc: increase debug capabilities Loic Pallardy
2017-11-06 17:09 ` Loic Pallardy
2017-11-06 17:09 ` [PATCH v2 1/2] remoteproc: debug: add resource table dump feature Loic Pallardy
2017-11-06 17:09   ` Loic Pallardy
2017-11-06 17:09 ` [PATCH v2 2/2] remoteproc: debug: add carveouts list " Loic Pallardy
2017-11-06 17:09   ` Loic Pallardy
2017-11-07  6:03 ` Bjorn Andersson [this message]
2017-11-07  8:19   ` [PATCH v2 0/2] remoteproc: increase debug capabilities Loic PALLARDY

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=20171107060331.GA22677@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --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 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.