From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, oss-drivers@corigine.com,
yinjun.zhang@corigine.com, richard.donkin@corigine.com,
niklas.soderlund@corigine.com
Subject: Re: [PATCH net] nfp: correct desc type when header dma len is 4096
Date: Sun, 04 Dec 2022 23:50:14 +0000 [thread overview]
Message-ID: <167019781474.13667.6835006524449338517.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221202134646.311108-1-simon.horman@corigine.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 Dec 2022 14:46:46 +0100 you wrote:
> From: Yinjun Zhang <yinjun.zhang@corigine.com>
>
> When there's only one buffer to dma and its length is 4096, then
> only one data descriptor is needed to carry it according to current
> descriptor definition. So the descriptor type should be `simple`
> instead of `gather`, the latter requires more than one descriptor,
> otherwise it'll be dropped by application firmware.
>
> [...]
Here is the summary with links:
- [net] nfp: correct desc type when header dma len is 4096
https://git.kernel.org/netdev/net/c/5c306de8f787
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-12-04 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 13:46 [PATCH net] nfp: correct desc type when header dma len is 4096 Simon Horman
2022-12-04 13:01 ` Leon Romanovsky
2022-12-04 23:50 ` 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=167019781474.13667.6835006524449338517.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=richard.donkin@corigine.com \
--cc=simon.horman@corigine.com \
--cc=yinjun.zhang@corigine.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.