[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <04bf6bd1-1150-ac57-5a8d-a9971148bd40@linaro.org>
Date: Fri, 6 Jan 2023 07:16:38 -0600
From: Alex Elder <elder@...aro.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
luca.weiss@...rphone.com, konrad.dybcio@...aro.org,
caleb.connolly@...aro.org, mka@...omium.org, evgreen@...omium.org,
andersson@...nel.org, quic_cpratapa@...cinc.com,
quic_avuyyuru@...cinc.com, quic_jponduru@...cinc.com,
quic_subashab@...cinc.com, elder@...nel.org,
netdev@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: ipa: correct IPA v4.7 IMEM offset
On 1/5/23 11:58 PM, Jakub Kicinski wrote:
> On Wed, 4 Jan 2023 12:10:17 -0600 Alex Elder wrote:
>> Note: This fixes a commit that first landed in v6.2-rc1.
>
> Why is it tagged for net-next then? 🤔️
> Let's treat it as a normal fix with a Fixes tag and for net.
> I reckon the commit message makes is sufficiently clear that
> I'm to blame :)
Sorry about that, I was confused, thinking it is only
needed in 6.2-rc--the current release cycle. But that's
not the way it works. I guess I wasn't fully recovered
from the holiday break.
I'll re-send and base it on net/master. Thanks.
-Alex
Powered by blists - more mailing lists