From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Suman Anna <s-anna@ti.com>
Cc: "ohad@wizery.com" <ohad@wizery.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
"praneeth@ti.com" <praneeth@ti.com>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"rogerq@kernel.org" <rogerq@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [External] : Re: [PATCH v2 0/5] Introduce PRU remoteproc consumer API
Date: Mon, 25 Jan 2021 15:56:20 +0000 [thread overview]
Message-ID: <886AD9CE-A967-4DBA-A212-A752040EE2BC@oracle.com> (raw)
In-Reply-To: <c5252e8d-094a-dcb7-7ccb-172e58ab3413@ti.com>
On Jan 25, 2021, at 7:43 AM, Suman Anna <s-anna@ti.com> wrote:
>
> Hi Santosh,
>
> On 1/24/21 10:34 PM, santosh.shilimkar@oracle.com wrote:
>> Hi Suman, Mathieu,
>>
>> On 1/7/21 2:49 PM, Suman Anna wrote:
>>> On 1/7/21 4:44 PM, Mathieu Poirier wrote:
>>>> On Wed, Jan 06, 2021 at 06:03:25PM -0600, Suman Anna wrote:
>>>>> Hi Mathieu,
>>>>>
>> [...]
>>>> I only see input from Andy and Lars in the thread you point out, nothing from
>>>> Greg. I have also taken a look at the patch [1] that made checkpatch complain
>>>> about ENOTSUPP. From what I see in that commit log the goal is to prevent new
>>>> additions of ENOTSUPP to the kernel.
>>>>
>>>> Please modify and resend, otherwise I'm sure someone will send another patch to
>>>> fix it before the end of the cycle.
>>>
>>> Yeah ok. I will send out a v3.
>>>
>> I haven't seen v3 of this series yet. Please post it
>> if you would like to include it for 5.12.
>
> This series is dependent on couple of patches that would have to come through
> the remoteproc tree first, and I need to post the next versions of those as
> well. So, let me sort out those first. You can drop this from your queue for 5.12.
>
Sounds good.
Regards,
Santosh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-25 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:52 [PATCH v2 0/5] Introduce PRU remoteproc consumer API Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 1/5] dt-bindings: remoteproc: Add PRU consumer bindings Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 2/5] remoteproc: pru: Add APIs to get and put the PRU cores Grzegorz Jaszczyk
2021-01-04 20:56 ` David Lechner
2020-12-16 16:52 ` [PATCH v2 3/5] remoteproc: pru: Deny rproc sysfs ops for PRU client driven boots Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 4/5] remoteproc: pru: Add pru_rproc_set_ctable() function Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 5/5] remoteproc: pru: Configure firmware based on client setup Grzegorz Jaszczyk
2021-01-04 20:11 ` [PATCH v2 0/5] Introduce PRU remoteproc consumer API David Lechner
2021-01-06 21:05 ` Suman Anna
2021-01-06 23:27 ` Mathieu Poirier
2021-01-07 0:03 ` Suman Anna
2021-01-07 22:44 ` Mathieu Poirier
2021-01-07 22:49 ` Suman Anna
2021-01-25 4:34 ` santosh.shilimkar
2021-01-25 15:43 ` Suman Anna
2021-01-25 15:56 ` Santosh Shilimkar [this message]
2021-12-26 13:00 ` Christian Gmeiner
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=886AD9CE-A967-4DBA-A212-A752040EE2BC@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.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).