From: Clement Leger <cleger@kalray.eu>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Clement Leger <cleger@kalray.eu>
Subject: [PATCH 0/2] remoteproc: add rproc_coredump_set_elf_info
Date: Fri, 10 Apr 2020 12:24:31 +0200 [thread overview]
Message-ID: <20200410102433.2672-1-cleger@kalray.eu> (raw)
This patch adds a way to set the elf informations that will be used to
generate the coredump. Second patch fixes drivers to use this function.
Clement Leger (2):
remoteproc: add rproc_coredump_set_elf_info
remoteproc: use rproc_coredump_set_elf_info in drivers
drivers/remoteproc/qcom_q6v5_adsp.c | 1 +
drivers/remoteproc/qcom_q6v5_mss.c | 3 ++
drivers/remoteproc/qcom_q6v5_pas.c | 1 +
drivers/remoteproc/qcom_wcnss.c | 1 +
drivers/remoteproc/remoteproc_core.c | 32 ++++++++++++++++++++--
drivers/remoteproc/remoteproc_elf_loader.c | 3 --
drivers/remoteproc/stm32_rproc.c | 1 +
include/linux/remoteproc.h | 2 ++
8 files changed, 39 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-10 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 10:24 Clement Leger [this message]
2020-04-10 10:24 ` [PATCH 1/2] remoteproc: add rproc_coredump_set_elf_info Clement Leger
2020-04-11 1:29 ` Bjorn Andersson
2020-04-17 19:38 ` Mathieu Poirier
2020-04-17 19:43 ` Clément Leger
2020-04-20 5:57 ` Bjorn Andersson
2020-04-10 10:24 ` [PATCH 2/2] remoteproc: use rproc_coredump_set_elf_info in drivers Clement Leger
2020-04-11 1:30 ` Bjorn Andersson
2020-04-17 19:39 ` Mathieu Poirier
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=20200410102433.2672-1-cleger@kalray.eu \
--to=cleger@kalray.eu \
--cc=agross@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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 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).