From: Raslan Darawsheh <rasland@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ali Alnubani <alialnu@nvidia.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH v2] doc: update recipe for static rdma-core in mlx guides
Date: Tue, 7 Mar 2023 11:16:04 +0000 [thread overview]
Message-ID: <MN2PR12MB30866A92E2A84ADED890ED89CFB79@MN2PR12MB3086.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230111084527.1255775-1-thomas@monjalon.net>
Hi,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, January 11, 2023 10:45 AM
> To: dev@dpdk.org
> Cc: Ali Alnubani <alialnu@nvidia.com>; bruce.richardson@intel.com; Matan
> Azrad <matan@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH v2] doc: update recipe for static rdma-core in mlx guides
>
> With recent versions of rdma-core, it becomes important to install the library
> after its compilation.
> If including rdma-core library from its build directory, some non-standard
> compiler tricks are used.
> When using an install directory for rdma-core, DPDK compilation is fine.
>
> While at it, disabling unneeded pyVerbs and man pages.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> v2: reword commit log
> ---
> doc/guides/nics/mlx4.rst | 3 ++-
> doc/guides/platform/mlx5.rst | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-03-07 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:16 [PATCH] " Thomas Monjalon
2022-12-08 11:33 ` Bruce Richardson
2023-01-11 8:45 ` [PATCH v2] " Thomas Monjalon
2023-03-07 11:16 ` Raslan Darawsheh [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=MN2PR12MB30866A92E2A84ADED890ED89CFB79@MN2PR12MB3086.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).