Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, luca.weiss@fairphone.com,
	dmitry.baryshkov@linaro.org, caleb.connolly@linaro.org,
	mka@chromium.org, evgreen@chromium.org, andersson@kernel.org,
	quic_cpratapa@quicinc.com, quic_avuyyuru@quicinc.com,
	quic_jponduru@quicinc.com, quic_subashab@quicinc.com,
	elder@kernel.org, netdev@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: ipa: fix a surprising number of bad offsets
Date: Tue, 14 Mar 2023 00:20:17 +0000	[thread overview]
Message-ID: <167875321706.19453.17373640129934893607.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230310193709.1477102-1-elder@linaro.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 10 Mar 2023 13:37:09 -0600 you wrote:
> A recent commit eliminated a hack that adjusted the offset used for
> many GSI registers.  It became possible because we now specify all
> GSI register offsets explicitly for every version of IPA.
> 
> Unfortunately, a large number of register offsets were *not* updated
> as they should have been in that commit.  For IPA v4.5+, the offset
> for every GSI register *except* the two inter-EE interrupt masking
> registers were supposed to have been reduced by 0xd000.
> 
> [...]

Here is the summary with links:
  - [net] net: ipa: fix a surprising number of bad offsets
    https://git.kernel.org/netdev/net/c/512dd354718b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-03-14  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 19:37 [PATCH net] net: ipa: fix a surprising number of bad offsets Alex Elder
2023-03-14  0:12 ` Jakub Kicinski
2023-03-14  0:20 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167875321706.19453.17373640129934893607.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andersson@kernel.org \
    --cc=caleb.connolly@linaro.org \
    --cc=davem@davemloft.net \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=edumazet@google.com \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=mka@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=quic_avuyyuru@quicinc.com \
    --cc=quic_cpratapa@quicinc.com \
    --cc=quic_jponduru@quicinc.com \
    --cc=quic_subashab@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox