[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3e01bc57-8667-4c56-2806-2ba009887bd4@linaro.org>
Date: Mon, 15 Mar 2021 11:50:15 -0500
From: Alex Elder <elder@...aro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: davem@...emloft.net, kuba@...nel.org, bjorn.andersson@...aro.org,
evgreen@...omium.org, cpratapa@...eaurora.org, elder@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] net: ipa: QMI fixes
On 3/15/21 11:38 AM, Manivannan Sadhasivam wrote:
> Hi Alex,
>
> On Mon, Mar 15, 2021 at 10:21:09AM -0500, Alex Elder wrote:
>> Mani Sadhasivam discovered some errors in the definitions of some
>> QMI messages used for IPA. This series addresses those errors,
>> and extends the definition of one message type to include some
>> newly-defined fields.
>>
>
> Thanks for the patches. I guess you need to add Fixes tag for patches 1,2 and
> they should be backported to stable.
I did not do that, intentionally. The reason is that the
existing code only supports IPA v3.5.1 and IPAv4.2. And
these bugs seem to cause no problems there.
There are some patches coming very soon that will add
more formal support for IPA v4.5 (where I know you
found these issues). Those will not be back-ported.
So these fixes don't appear to be necessary for existing
supported platforms.
If you still believe I should have these back-ported,
I have no objection to re-posting for that. But I
wanted to explain my reasoning before doing it.
--> Do you still think I should have these back-ported?
Thanks.
-Alex
>
> Thanks,
> Mani
>
>> -Alex
>>
>> Alex Elder (3):
>> net: ipa: fix a duplicated tlv_type value
>> net: ipa: fix another QMI message definition
>> net: ipa: extend the INDICATION_REGISTER request
>>
>> drivers/net/ipa/ipa_qmi_msg.c | 78 +++++++++++++++++++++++++++++++----
>> drivers/net/ipa/ipa_qmi_msg.h | 6 ++-
>> 2 files changed, 74 insertions(+), 10 deletions(-)
>>
>> --
>> 2.27.0
>>
Powered by blists - more mailing lists