From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63990net/mlx5: add define of LRO segment chunk size
Date: 20 Jan 2020 09:35:13 -0800 [thread overview]
Message-ID: <ee68f5$94o5hc@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/63990
_apply issues_
Submitter: Dekel Peled <dekelp@mellanox.com>
Date: 2019-12-18 07:51:39
Reply_mail: 9e1ca71b1fd1da5830f44e74f8b12ba7a088a357.1576654991.git.dekelp@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: fa90b251e1f96190604558e71ad70dd046a0c236
Repo:dpdk, CommitID: 03bff90ccfd6ad347f1e50901caf47890872ca28
*Repo: dpdk-next-net-mlx
#define MLX5_MAX_LRO_SIZE (UINT8_MAX * 256u)
/* LRO configurations structure. */
struct mlx5_lro_config {
error: patch failed: drivers/net/mlx5/mlx5.h:218
error: drivers/net/mlx5/mlx5.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_rxq.c...
error: while searching for:
*
* @param dev
--
mlx5_max_lro_msg_size_adjust(struct rte_eth_dev *dev, uint32_t max_lro_size)
{
struct mlx5_priv *priv = dev->data->dev_private;
error: patch failed: drivers/net/mlx5/mlx5_rxq.c:1717
error: drivers/net/mlx5/mlx5_rxq.c: patch does not apply
*Repo: dpdk
#define MLX5_MAX_LRO_SIZE (UINT8_MAX * 256u)
/* LRO configurations structure. */
struct mlx5_lro_config {
error: patch failed: drivers/net/mlx5/mlx5.h:218
error: drivers/net/mlx5/mlx5.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_rxq.c...
error: while searching for:
*
* @param dev
--
mlx5_max_lro_msg_size_adjust(struct rte_eth_dev *dev, uint32_t max_lro_size)
{
struct mlx5_priv *priv = dev->data->dev_private;
error: patch failed: drivers/net/mlx5/mlx5_rxq.c:1717
error: drivers/net/mlx5/mlx5_rxq.c: patch does not apply
DPDK STV team
next reply other threads:[~2020-01-20 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 17:35 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-18 8:43 sys_stv
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='ee68f5$94o5hc@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@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).