[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230105215806.4c192dad@kernel.org>
Date:   Thu, 5 Jan 2023 21:58:06 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Alex Elder <elder@...aro.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 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 :)
Powered by blists - more mailing lists
 
