[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4db58974-691d-aae6-adc5-09f0611b7251@oracle.com>
Date: Fri, 11 Sep 2020 21:54:07 -0700
From: "santosh.shilimkar@...cle.com" <santosh.shilimkar@...cle.com>
To: Nishanth Menon <nm@...com>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Tero Kristo <t-kristo@...com>,
Rob Herring <robh+dt@...nel.org>,
Vignesh Raghavendra <vigneshr@...com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Sekhar Nori <nsekhar@...com>
Subject: Re: [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support
On 9/9/20 9:52 AM, santosh.shilimkar@...cle.com wrote:
> On 9/2/20 7:08 AM, Nishanth Menon wrote:
>> On 11:34-20200831, santosh.shilimkar@...cle.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
Powered by blists - more mailing lists