From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <alialnu@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH] doc: update recipe for static rdma-core in mlx guides
Date: Thu, 8 Dec 2022 11:33:13 +0000 [thread overview]
Message-ID: <Y5HLedfF7nkrJbAI@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20221208111646.1487459-1-thomas@monjalon.net>
On Thu, Dec 08, 2022 at 12:16:46PM +0100, Thomas Monjalon wrote:
> With recent versions of rdma-core, it becomes important to install,
> so some non-standard compiler tricks are avoided.
>
I think this paragraph could do with a bit more explanation in it, e.g. to
clarify that this is (presumably) installing package vs working with it in
build directory.
/Bruce
next prev parent reply other threads:[~2022-12-08 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:16 Thomas Monjalon
2022-12-08 11:33 ` Bruce Richardson [this message]
2023-01-11 8:45 ` [PATCH v2] " Thomas Monjalon
2023-03-07 11:16 ` Raslan Darawsheh
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=Y5HLedfF7nkrJbAI@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=alialnu@nvidia.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).