From: patchwork-bot+netdevbpf@kernel.org
To: David Christensen <drc@linux.ibm.com>
Cc: shannon.nelson@amd.com, brett.creeley@amd.com,
drivers@pensando.io, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] ionic: advertise 52-bit addressing limitation for MSI-X
Date: Wed, 05 Jun 2024 23:00:34 +0000 [thread overview]
Message-ID: <171762843403.9199.12097128294110866724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240603212747.1079134-1-drc@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 3 Jun 2024 17:27:41 -0400 you wrote:
> Current ionic devices only support 52 internal physical address
> lines. This is sufficient for x86_64 systems which have similar
> limitations but does not apply to all other architectures,
> notably IBM POWER (ppc64). To ensure that MSI/MSI-X vectors are
> not set outside the physical address limits of the NIC, set the
> no_64bit_msi value of the pci_dev structure during device probe.
>
> [...]
Here is the summary with links:
- [net-next,v2] ionic: advertise 52-bit addressing limitation for MSI-X
https://git.kernel.org/netdev/net-next/c/1467713eb224
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:[~2024-06-05 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:40 [PATCH net-next] ionic: advertise 52-bit addressing limitation for MSI-X David Christensen
2024-05-30 22:34 ` Nelson, Shannon
2024-06-03 21:27 ` [PATCH net-next v2] " David Christensen
2024-06-03 22:16 ` Nelson, Shannon
2024-06-05 23: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=171762843403.9199.12097128294110866724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drc@linux.ibm.com \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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;
as well as URLs for NNTP newsgroup(s).