From: Tanmay Shah <tanmay.shah@amd.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: mathieu.poirier@linaro.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] remoteproc: get rproc devices for clusters
Date: Wed, 22 Mar 2023 10:37:16 -0700 [thread overview]
Message-ID: <d77a3ca0-0e84-45ca-274d-5d1229d34e6c@amd.com> (raw)
In-Reply-To: <20230322141215.ygicmrppqaawlgeb@ripper>
On 3/22/23 7:12 AM, Bjorn Andersson wrote:
> On Tue, Mar 21, 2023 at 09:09:32PM -0700, Tanmay Shah wrote:
>> This series extends original patch and makes rproc_put() work
>> for clusters along with rprog_get_by_phandle().
>>
>> v1 is here: https://lore.kernel.org/all/20221214221643.1286585-1-mathieu.poirier@linaro.org/
>>
> What changed since v1?
Hello Bjorn,
Thanks for reviews.
rproc_put() is fixed in v2. I will add proper change-log in cover-letter
in next revision.
Thanks,
> Thanks,
> Bjorn
>
>> Mathieu Poirier (1):
>> remoteproc: Make rproc_get_by_phandle() work for clusters
>>
>> Tanmay Shah (1):
>> remoteproc: enhance rproc_put() for clusters
>>
>> drivers/remoteproc/remoteproc_core.c | 41 +++++++++++++++++++++++++++-
>> 1 file changed, 40 insertions(+), 1 deletion(-)
>>
>>
>> base-commit: e19967994d342a5986d950a1bfddf19d7e1191b7
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2023-03-22 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 4:09 [PATCH v2 0/2] remoteproc: get rproc devices for clusters Tanmay Shah
2023-03-22 4:09 ` [PATCH v2 1/2] remoteproc: Make rproc_get_by_phandle() work " Tanmay Shah
2023-03-22 4:09 ` [PATCH v2 2/2] remoteproc: enhance rproc_put() " Tanmay Shah
2023-03-22 6:20 ` kernel test robot
2023-03-22 7:31 ` kernel test robot
2023-03-22 11:52 ` Dan Carpenter
2023-03-22 16:05 ` Mathieu Poirier
2023-03-22 17:34 ` Tanmay Shah
2023-03-23 22:45 ` Mathieu Poirier
2023-03-22 14:12 ` [PATCH v2 0/2] remoteproc: get rproc devices " Bjorn Andersson
2023-03-22 16:11 ` Mathieu Poirier
2023-03-22 17:37 ` Tanmay Shah [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=d77a3ca0-0e84-45ca-274d-5d1229d34e6c@amd.com \
--to=tanmay.shah@amd.com \
--cc=andersson@kernel.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