mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Arnaud Pouliquen <arnaud.pouliquen@st.com>,
	Loic Pallardy <loic.pallardy@st.com>,
	Tero Kristo <t-kristo@ti.com>, <linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] Misc. rproc fixes around fixed memory region support
Date: Fri, 8 May 2020 10:14:49 -0500	[thread overview]
Message-ID: <0a2aa179-9a97-003d-d682-283a8c354ea7@ti.com> (raw)
In-Reply-To: <181b6c56-420c-f306-f2cf-53380ad1f37b@ti.com>

Hi Bjorn,

On 5/2/20 1:29 PM, Suman Anna wrote:
> Hi Bjorn,
> 
> On 4/20/20 11:05 AM, Suman Anna wrote:
>> Hi Bjorn,
>>
>> This is another minor revision of the fixes around fixed memory region
>> support [1] series. Patch 1 is revised to go back to the logic used in v1
>> after a long discussion on the v2 version [2]. The other suggestions can
>> be future improvments as they would require corresponding platform driver
>> changes. Please look through the discussion there and let us know your
>> preference. Patches are based on v5.7-rc1.
>>
>> I really appreciate it if you can target the series for the current 
>> 5.7 -rc's.
>> The fixes would apply for all 5.1+ kernels.
> 
> Ping on these.

The patches have been reviewed and/or acked by both Mathieu and Arnaud.
Can you please get these into the current -rc's?

Thanks,
Suman

> 
> regards
> Suman
> 
>>
>> Please see the v1 cover-letter [1] for the details on the issues.
>>
>> regards
>> Suman
>>
>> [1] https://patchwork.kernel.org/cover/11422723/
>> [2] https://patchwork.kernel.org/comment/23274389/
>>
>> Suman Anna (1):
>>    remoteproc: Fix and restore the parenting hierarchy for vdev
>>
>> Tero Kristo (1):
>>    remoteproc: Fall back to using parent memory pool if no dedicated
>>      available
>>
>>   drivers/remoteproc/remoteproc_core.c   |  2 +-
>>   drivers/remoteproc/remoteproc_virtio.c | 12 ++++++++++++
>>   2 files changed, 13 insertions(+), 1 deletion(-)
>>
> 


  reply	other threads:[~2020-05-08 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 16:05 Suman Anna
2020-04-20 16:05 ` [PATCH v3 1/2] remoteproc: Fall back to using parent memory pool if no dedicated available Suman Anna
2020-05-07 15:52   ` Arnaud POULIQUEN
2020-05-08 22:27   ` Mathieu Poirier
2020-04-20 16:06 ` [PATCH v3 2/2] remoteproc: Fix and restore the parenting hierarchy for vdev Suman Anna
2020-05-02 18:29 ` [PATCH v3 0/2] Misc. rproc fixes around fixed memory region support Suman Anna
2020-05-08 15:14   ` Suman Anna [this message]
2020-05-12 23:10     ` Bjorn Andersson
2020-05-13  9:50       ` Tero Kristo

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=0a2aa179-9a97-003d-d682-283a8c354ea7@ti.com \
    --to=s-anna@ti.com \
    --cc=arnaud.pouliquen@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=t-kristo@ti.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

all inboxes | Powered by JetHome®