From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@oktetlabs.ru>, dev@dpdk.org
Cc: Andy Moreton <amoreton@xilinx.com>, stable@dpdk.org
Subject: Re: [PATCH 1/3] common/sfc_efx/base: fix assignment of maximum Tx data count
Date: Wed, 28 Sep 2022 12:54:09 +0300 [thread overview]
Message-ID: <74d86f07-951b-20fd-562c-a91b9aab3c07@oktetlabs.ru> (raw)
In-Reply-To: <20220812122454.1947322-1-ivan.malov@oktetlabs.ru>
On 8/12/22 15:24, Ivan Malov wrote:
> Maximum data count of a Tx descriptor is advertised to users,
> however, this value is mistakenly derived from the Rx define.
> Use the Tx one instead. The resulting value will be the same.
>
> Fixes: 1e43fe3cb41e ("net/sfc/base: separate limitations on Tx DMA descriptors")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-09-28 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 12:24 Ivan Malov
2022-09-28 9:54 ` Andrew Rybchenko [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=74d86f07-951b-20fd-562c-a91b9aab3c07@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=amoreton@xilinx.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
--cc=stable@dpdk.org \
/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).