From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/5] Update docs for installing on FreeBSD
Date: Sun, 16 Feb 2020 11:04:34 +0100 [thread overview]
Message-ID: <4005637.rE2NhlSrgm@xps> (raw)
In-Reply-To: <20200103153256.2895527-1-bruce.richardson@intel.com>
03/01/2020 16:32, Bruce Richardson:
> Update the FreeBSD GSG guide to cover:
>
> * installing from package as well as via ports collection
> * building and installing manually via meson and ninja
> * building examples using the pkg-config file, since both the port/pkg
> and building from source use meson.
> * other general tidy-up.
>
> Bruce Richardson (5):
> doc: update intro to FreeBSD GSG
> doc: document installing from FreeBSD package
> doc: add meson install instructions for FreeBSD
> doc: update section on loading FreeBSD kernel modules
> doc: update documentation on build and running FreeBSD apps
Applied, thanks
prev parent reply other threads:[~2020-02-16 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 15:32 Bruce Richardson
2020-01-03 15:32 ` [dpdk-dev] [PATCH 1/5] doc: update intro to FreeBSD GSG Bruce Richardson
2020-01-03 15:32 ` [dpdk-dev] [PATCH 2/5] doc: document installing from FreeBSD package Bruce Richardson
2020-01-03 15:32 ` [dpdk-dev] [PATCH 3/5] doc: add meson install instructions for FreeBSD Bruce Richardson
2020-01-03 15:32 ` [dpdk-dev] [PATCH 4/5] doc: update section on loading FreeBSD kernel modules Bruce Richardson
2020-01-03 15:32 ` [dpdk-dev] [PATCH 5/5] doc: update documentation on build and running FreeBSD apps Bruce Richardson
2020-02-16 10:04 ` 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=4005637.rE2NhlSrgm@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).