From: Thomas Monjalon <thomas@monjalon.net>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Olga Shern <olgas@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add mlx4 CRC stripping toggling limitation
Date: Tue, 08 May 2018 14:34:29 +0200 [thread overview]
Message-ID: <1663463.84SeaxCa5g@xps> (raw)
In-Reply-To: <1525782629-897-1-git-send-email-ophirmu@mellanox.com>
08/05/2018 14:30, Ophir Munk:
> +Limitations
> +-----------
> +
> +- CRC stripping is supported by default and this capability is always reported
> + as "true". The ability to enable/disable CRC stripping requires OFED version
> + 4.3-1.5.0.0 or rdma-core version v18.
I think it is better to merge this patch with the one fixing the capability.
So we will be able to refer to one atomic commit in the history.
next prev parent reply other threads:[~2018-05-08 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:30 Ophir Munk
2018-05-08 12:34 ` Thomas Monjalon [this message]
2018-05-09 10:07 ` Shahaf Shuler
2018-05-09 10:31 ` Ophir Munk
2018-05-09 11:12 ` Shahaf Shuler
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=1663463.84SeaxCa5g@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=shahafs@mellanox.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;
as well as URLs for NNTP newsgroup(s).