From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support
Date: Fri, 11 Sep 2020 21:54:07 -0700 [thread overview]
Message-ID: <4db58974-691d-aae6-adc5-09f0611b7251@oracle.com> (raw)
In-Reply-To: <0b24a619-060a-1abb-76d9-218b5db18f11@oracle.com>
On 9/9/20 9:52 AM, santosh.shilimkar@oracle.com wrote:
> On 9/2/20 7:08 AM, Nishanth Menon wrote:
>> On 11:34-20200831, santosh.shilimkar@oracle.com wrote:
>>> On 8/29/20 11:41 AM, Grygorii Strashko wrote:
[..]
>>
>>
>> Santosh, in this series, may i suggest that the dtsi changes[1] be hosted
>> on my tree? else we are going to create a mix of rc1 and rc3 branches
>> which is going to be irritating, to say the least.
>>
>> I will pick [1] the day after I see the patches 1 and 2 in linux-next
>> tag.
>>
> Sure !!
Applied. Should show up in linux-next
_______________________________________________
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:[~2020-09-12 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 18:41 [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 1/3] " Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 2/3] bindings: soc: ti: soc: ringacc: remove ti, dma-ring-reset-quirk Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 3/3] arm64: dts: ti: k3-am65: ringacc: drop " Grygorii Strashko
2020-08-31 18:34 ` [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support santosh.shilimkar
2020-09-02 14:08 ` Nishanth Menon
2020-09-09 16:52 ` santosh.shilimkar
2020-09-12 4:54 ` santosh.shilimkar [this message]
2020-09-08 22:09 ` Suman Anna
2020-09-09 2:40 ` santosh.shilimkar
2020-09-12 4:55 ` santosh.shilimkar
2020-09-14 12:34 ` Nishanth Menon
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=4db58974-691d-aae6-adc5-09f0611b7251@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vigneshr@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;
as well as URLs for NNTP newsgroup(s).