From: Thomas Monjalon <thomas@monjalon.net>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
stable@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-stable] [PATCH] doc/prog_guide: fix formatting of notes in meson chapter
Date: Mon, 05 Oct 2020 23:57:38 +0200 [thread overview]
Message-ID: <2610099.c85sH34g6k@thomas> (raw)
In-Reply-To: <SN6PR11MB308642F3FDDA7CBD02A60474FC2D0@SN6PR11MB3086.namprd11.prod.outlook.com>
> > The "note" callouts in the chapter describing the meson build were
> > incorrectly formatted, so adjust to use the correct markdown syntax.
> >
> > Fixes: 9c3adc289c5e ("doc: add instructions on build using meson")
> > Cc: stable@dpdk.org
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2020-10-05 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:00 Bruce Richardson
2020-09-04 8:05 ` Mcnamara, John
2020-10-05 21:57 ` 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=2610099.c85sH34g6k@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).