From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Suman Anna <s-anna@ti.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] rproc core patches needed for TI K3 drivers
Date: Thu, 16 Apr 2020 19:20:34 -0500 [thread overview]
Message-ID: <20200417002036.24359-1-s-anna@ti.com> (raw)
Hi Bjorn, Mathieu,
The following 2 patches were a revised version and split out from the
TI K3 R5F remoteproc support patch series [1]. The patches do use the
cleanup logic from Mathieu's "remoteproc: Refactor function rproc_alloc()"
series. The patches address both of your comments.
Delta changes in individual patches.
regards
Suman
[1] https://patchwork.kernel.org/cover/11456367/
[2] https://patchwork.kernel.org/cover/11492005/
Loic Pallardy (1):
remoteproc: Add prepare and unprepare ops
Suman Anna (1):
remoteproc: Use a local copy for the name field
drivers/remoteproc/remoteproc_core.c | 21 +++++++++++++++++++--
drivers/remoteproc/remoteproc_internal.h | 16 ++++++++++++++++
include/linux/remoteproc.h | 4 ++++
3 files changed, 39 insertions(+), 2 deletions(-)
--
2.26.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-17 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 0:20 Suman Anna [this message]
2020-04-17 0:20 ` [PATCH 1/2] remoteproc: Add prepare and unprepare ops Suman Anna
2020-04-21 2:52 ` Bjorn Andersson
2020-04-21 14:12 ` Suman Anna
2020-04-23 5:01 ` Bjorn Andersson
2020-04-17 0:20 ` [PATCH 2/2] remoteproc: Use a local copy for the name field Suman Anna
2020-04-17 17:04 ` Mathieu Poirier
2020-04-20 4:59 ` Bjorn Andersson
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=20200417002036.24359-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
/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).