From: patchwork-bot+netdevbpf@kernel.org
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: elder@linaro.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jami.kettunen@somainline.org,
elder@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] net: ipa: fix v3.5.1 resource limit max values
Date: Wed, 26 Oct 2022 03:00:16 +0000 [thread overview]
Message-ID: <166675321627.7735.13125128064237036684.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221024210336.4014983-1-caleb.connolly@linaro.org>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Oct 2022 22:03:31 +0100 you wrote:
> Some resource limits on IPA v3.5.1 have their max values set to
> 255, this causes a few splats in ipa_reg_encode and prevents the
> IPA from booting properly. The limits are all 6 bits wide so
> adjust the max values to 63.
>
> Fixes: 1c418c4a929c ("net: ipa: define resource group/type IPA register fields")
> Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
>
> [...]
Here is the summary with links:
- [v2,1/2] net: ipa: fix v3.5.1 resource limit max values
https://git.kernel.org/netdev/net/c/f23a566bbfc0
- [v2,2/2] net: ipa: fix v3.1 resource limit masks
https://git.kernel.org/netdev/net/c/05a31b94af32
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-26 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 21:03 Caleb Connolly
2022-10-24 21:03 ` [PATCH v2 2/2] net: ipa: fix v3.1 resource limit masks Caleb Connolly
2022-10-24 21:36 ` Alex Elder
2022-10-25 20:03 ` Jami Kettunen
2022-10-24 21:36 ` [PATCH v2 1/2] net: ipa: fix v3.5.1 resource limit max values Alex Elder
2022-10-26 3:00 ` 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=166675321627.7735.13125128064237036684.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=jami.kettunen@somainline.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®