From: patchwork-bot+netdevbpf@kernel.org
To: Michal Schmidt <mschmidt@redhat.com>
Cc: michalx.jaron@intel.com, mateusz.palczewski@intel.com,
leyi.rong@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, jacob.e.keller@intel.com,
pabeni@redhat.com
Subject: Re: [Intel-wired-lan] [PATCH net] ice: always add legacy 32byte RXDID in supported_rxdids
Date: Thu, 28 Sep 2023 12:10:24 +0000 [thread overview]
Message-ID: <169590302402.1991.14030271738897322227.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920115439.61172-1-mschmidt@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 20 Sep 2023 13:54:38 +0200 you wrote:
> When the PF and VF drivers both support flexible rx descriptors and have
> negotiated the VIRTCHNL_VF_OFFLOAD_RX_FLEX_DESC capability, the VF driver
> queries the PF for the list of supported descriptor formats
> (VIRTCHNL_OP_GET_SUPPORTED_RXDIDS). The PF driver is supposed to set the
> supported_rxdids bits that correspond to the descriptor formats the
> firmware implements. The legacy 32-byte rx desc format is always
> supported, even though it is not expressed in GLFLXP_RXDID_FLAGS.
>
> [...]
Here is the summary with links:
- [net] ice: always add legacy 32byte RXDID in supported_rxdids
https://git.kernel.org/netdev/net/c/c070e51db5e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-09-28 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:54 [Intel-wired-lan] [PATCH net] ice: always add legacy 32byte RXDID in supported_rxdids Michal Schmidt
2023-09-20 14:08 ` Przemek Kitszel
2023-09-20 21:30 ` Jacob Keller
2023-09-28 12:10 ` 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=169590302402.1991.14030271738897322227.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=leyi.rong@intel.com \
--cc=mateusz.palczewski@intel.com \
--cc=michalx.jaron@intel.com \
--cc=mschmidt@redhat.com \
--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