From: patchwork-bot+netdevbpf@kernel.org
To: Louis Amas <louis.amas@eho.link>
Cc: mw@semihalf.com, linux@armlinux.org.uk, davem@davemloft.net,
kuba@kernel.org, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
kpsingh@kernel.org, mcroce@microsoft.com,
emmanuel.deloget@eho.link, brouer@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v5 net 1/1] net: mvpp2: fix XDP rx queues registering
Date: Thu, 09 Dec 2021 02:40:08 +0000 [thread overview]
Message-ID: <163901760858.2130.12295890768510315552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211207143423.916334-1-louis.amas@eho.link>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Dec 2021 15:34:22 +0100 you wrote:
> The registration of XDP queue information is incorrect because the
> RX queue id we use is invalid. When port->id == 0 it appears to works
> as expected yet it's no longer the case when port->id != 0.
>
> The problem arised while using a recent kernel version on the
> MACCHIATOBin. This board has several ports:
> * eth0 and eth1 are 10Gbps interfaces ; both ports has port->id == 0;
> * eth2 is a 1Gbps interface with port->id != 0.
>
> [...]
Here is the summary with links:
- [v5,net,1/1] net: mvpp2: fix XDP rx queues registering
https://git.kernel.org/netdev/net/c/a50e659b2a1b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-12-09 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 14:34 [PATCH v5 net 1/1] net: mvpp2: fix XDP rx queues registering Louis Amas
2021-12-09 2:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-10 17:16 Louis Amas
2021-12-12 13:56 ` Greg KH
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=163901760858.2130.12295890768510315552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=emmanuel.deloget@eho.link \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=louis.amas@eho.link \
--cc=mcroce@microsoft.com \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.