From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: stable@dpdk.org, Declan Doherty <declan.doherty@intel.com>,
Chas Williams <chas3@att.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] test/bonding: don't request CRC STRIP offload
Date: Thu, 26 Jul 2018 21:46:15 +0200 [thread overview]
Message-ID: <16480768.J1H9DbpJ65@xps> (raw)
In-Reply-To: <20180720155941.35021-1-ferruh.yigit@intel.com>
20/07/2018 17:59, Ferruh Yigit:
> bonding PMD doesn't announce CRC STRIP offload support, don't request
> this offload in unit test otherwise unit test fails.
>
> Fixes: f52f1a65e461 ("ethdev: force offloading API rules")
> Cc: stable@dpdk.org
>
> Reported-by: Meijuan Zhao <meijuanx.zhao@intel.com>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-07-26 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 15:59 [dpdk-dev] " Ferruh Yigit
2018-07-26 19:46 ` Thomas Monjalon [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=16480768.J1H9DbpJ65@xps \
--to=thomas@monjalon.net \
--cc=chas3@att.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).