From: santosh.shilimkar@oracle.com
To: Suman Anna <s-anna@ti.com>
Cc: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
devicetree@vger.kernel.org, tony@atomide.com,
linux-kernel@vger.kernel.org, praneeth@ti.com,
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] dt-bindings: soc: ti: Update TI PRUSS bindings about schemas to include
Date: Tue, 19 Jan 2021 08:57:43 -0800 [thread overview]
Message-ID: <a080a917-9c37-088b-075b-7b5a5d49256d@oracle.com> (raw)
In-Reply-To: <6f5b6609-bb9e-31f7-c0c2-3bb261a54d6a@ti.com>
On 1/15/21 8:38 AM, Suman Anna wrote:
> Hi Santosh,
>
> On 12/21/20 3:32 PM, Rob Herring wrote:
>> On Wed, 16 Dec 2020 23:50:27 +0100, Grzegorz Jaszczyk wrote:
>>> Now after ti,pruss-intc.yaml and ti,pru-rproc.yaml are merged, include
>>> them in proper property and extend the examples section.
>>>
>>> At the occasion extend the allowed property list about dma-ranges.
>>>
>>> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
>>> ---
>>> .../devicetree/bindings/soc/ti/ti,pruss.yaml | 76 +++++++++++++++++++
>>> 1 file changed, 76 insertions(+)
>>>
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>>
>
> Gentle reminder, I haven't seen this patch yet on linux-next.
> Can you please pick this up for 5.12.
>
Yes, will look into it this week.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-01-19 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 22:50 [PATCH] dt-bindings: soc: ti: Update TI PRUSS bindings about schemas to include Grzegorz Jaszczyk
2020-12-21 21:32 ` Rob Herring
2021-01-15 16:38 ` Suman Anna
2021-01-19 16:57 ` santosh.shilimkar [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=a080a917-9c37-088b-075b-7b5a5d49256d@oracle.com \
--to=santosh.shilimkar@oracle.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=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).