From: Suman Anna <s-anna@ti.com>
To: David Lechner <david@lechnology.com>, <grzegorz.jaszczyk@linaro.org>
Cc: <bjorn.andersson@linaro.org>, <devicetree@vger.kernel.org>,
<lee.jones@linaro.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <mathieu.poirier@linaro.org>,
<ohad@wizery.com>, <praneeth@ti.com>, <robh+dt@kernel.org>,
<rogerq@kernel.org>, <ssantosh@kernel.org>
Subject: Re: [PATCH v2 0/5] Introduce PRU remoteproc consumer API
Date: Wed, 6 Jan 2021 15:05:16 -0600 [thread overview]
Message-ID: <3be186ef-5f1b-c3c7-f6c9-ccac6ebecaf7@ti.com> (raw)
In-Reply-To: <9603a894-495b-3c73-0916-aea52f98fe9f@lechnology.com>
Hi David,
On 1/4/21 2:11 PM, David Lechner wrote:
>
>> Please see the individual patches for exact changes in each patch, following is
>> the only change from v1:
>> - Change the 'prus' property name to 'ti,prus' as suggested by Rob Herring,
>> which influences patch #1 and patch #2
>
> It looks like "soc: ti: pruss: Add pruss_{request, release}_mem_region() API"
> was also dropped in v2. Was this intentional?
No, it is not dropped. That patch is part of a different similarly titled
"Introduce PRU platform consumer API" series [1], which is dependent on this
series and is against a different folder (maintainer): drivers/soc/ti.
regards
Suman
[1] https://patchwork.kernel.org/project/linux-remoteproc/list/?series=400787
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: David Lechner <david@lechnology.com>, <grzegorz.jaszczyk@linaro.org>
Cc: ohad@wizery.com, devicetree@vger.kernel.org,
mathieu.poirier@linaro.org, praneeth@ti.com,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
bjorn.andersson@linaro.org, rogerq@kernel.org,
robh+dt@kernel.org, ssantosh@kernel.org,
linux-omap@vger.kernel.org, lee.jones@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] Introduce PRU remoteproc consumer API
Date: Wed, 6 Jan 2021 15:05:16 -0600 [thread overview]
Message-ID: <3be186ef-5f1b-c3c7-f6c9-ccac6ebecaf7@ti.com> (raw)
In-Reply-To: <9603a894-495b-3c73-0916-aea52f98fe9f@lechnology.com>
Hi David,
On 1/4/21 2:11 PM, David Lechner wrote:
>
>> Please see the individual patches for exact changes in each patch, following is
>> the only change from v1:
>> - Change the 'prus' property name to 'ti,prus' as suggested by Rob Herring,
>> which influences patch #1 and patch #2
>
> It looks like "soc: ti: pruss: Add pruss_{request, release}_mem_region() API"
> was also dropped in v2. Was this intentional?
No, it is not dropped. That patch is part of a different similarly titled
"Introduce PRU platform consumer API" series [1], which is dependent on this
series and is against a different folder (maintainer): drivers/soc/ti.
regards
Suman
[1] https://patchwork.kernel.org/project/linux-remoteproc/list/?series=400787
_______________________________________________
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-06 21:08 UTC|newest]
Thread overview: 36+ 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 ` 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 ` Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 2/5] remoteproc: pru: Add APIs to get and put the PRU cores Grzegorz Jaszczyk
2020-12-16 16:52 ` Grzegorz Jaszczyk
2021-01-04 20:56 ` David Lechner
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 ` Grzegorz Jaszczyk
2020-12-17 22:43 ` kernel test robot
2020-12-17 22:43 ` kernel test robot
2020-12-16 16:52 ` [PATCH v2 4/5] remoteproc: pru: Add pru_rproc_set_ctable() function Grzegorz Jaszczyk
2020-12-16 16:52 ` Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 5/5] remoteproc: pru: Configure firmware based on client setup Grzegorz Jaszczyk
2020-12-16 16:52 ` Grzegorz Jaszczyk
2021-01-04 20:11 ` [PATCH v2 0/5] Introduce PRU remoteproc consumer API David Lechner
2021-01-04 20:11 ` David Lechner
2021-01-06 21:05 ` Suman Anna [this message]
2021-01-06 21:05 ` Suman Anna
2021-01-06 23:27 ` Mathieu Poirier
2021-01-06 23:27 ` Mathieu Poirier
2021-01-07 0:03 ` Suman Anna
2021-01-07 0:03 ` Suman Anna
2021-01-07 22:44 ` Mathieu Poirier
2021-01-07 22:44 ` Mathieu Poirier
2021-01-07 22:49 ` Suman Anna
2021-01-07 22:49 ` Suman Anna
2021-01-25 4:34 ` santosh.shilimkar
2021-01-25 4:34 ` santosh.shilimkar
2021-01-25 15:43 ` Suman Anna
2021-01-25 15:43 ` Suman Anna
2021-01-25 15:56 ` [External] : " Santosh Shilimkar
2021-01-25 15:56 ` Santosh Shilimkar
2021-12-26 13:00 ` Christian Gmeiner
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=3be186ef-5f1b-c3c7-f6c9-ccac6ebecaf7@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=david@lechnology.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.