Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 0/4] slimbus: patches (set 1) for 5.15
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org
References: <20210806091639.532-1-srinivas.kandagatla@linaro.org>
 <YQ03FPyxF8DFlwI7@kroah.com>
 <71200533-db05-157f-480a-d64812e1d9c2@linaro.org>
 <YQ6EMKD0gOIJn+FL@kroah.com>
From:   Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Message-ID: <e737f324-400e-824b-3865-017d2d2a5543@linaro.org>
Date:   Sat, 7 Aug 2021 14:04:39 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <YQ6EMKD0gOIJn+FL@kroah.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 07/08/2021 14:01, Greg KH wrote:
> On Sat, Aug 07, 2021 at 11:48:48AM +0100, Srinivas Kandagatla wrote:
>>
>>
>> On 06/08/2021 14:20, Greg KH wrote:
>>> On Fri, Aug 06, 2021 at 10:16:35AM +0100, Srinivas Kandagatla wrote:
>>>> Hi Greg,
>>>>
>>>> Recently runtime pm testing on slimbus reveled that its
>>>> totally broken on SlimBus ngd drivers.
>>>>
>>>> Below are the fixes to get it back working.
>>>>
>>>> - One of the reason begin incorrect device pointer used for
>>>> runtime pm and in some places
>>>>
>>>> - Second one was to do with unable to validate transaction id
>>>>    which resulted in negative runtime pm count.
>>>>
>>>> - Other fix was to do with resetting dma addresses once ngd
>>>> controller is power-cycled.
>>>>
>>>> With all these fixed runtime pm is now fully functional on NGD
>>>> controllers.
>>>>
>>>> Currently I marked them all with Cc: <stable@vger.kernel.org>
>>>> as these all patches are required to fix runtime pm on SlimBus
>>>> NGD controller.
>>>>
>>>> Can you please queue them up for 5.15.
>>>
>>> Why do you want these for 5.15-rc1 when you need them to fix problems in
>>> 5.14?  Shouldn't they go into 5.14-final?
>>
>> Yes, these should go to other stable trees aswell.
>> I assumed that Fixes tag will automatically backport those patches.
> 
> Yes, but that can not happen until they hit Linus's tree, which would
> not be until 5.15-rc1.  Do you want to delay until that long from now?
> 
> How about splitting this into 2 patch series, one that you want to see
> get into 5.14-final, and one for 5.15-rc1.

All the patches in these series are fixes so the can go to 5.14-final.

--srini
> 
> thanks,
> 
> greg k-h
>