From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Marko Kovacevic <marko.kovacevic@intel.com>, dev@dpdk.org
Cc: john.mcnamara@intel.com, bernard.iremonger@intel.com
Subject: Re: [PATCH v1] doc: fix sample application formatting
Date: Tue, 16 Oct 2018 16:08:48 +0100 [thread overview]
Message-ID: <6db5b5b0-2d82-6292-22f1-bb088e9e9dd4@intel.com> (raw)
In-Reply-To: <20180816163538.4797-1-marko.kovacevic@intel.com>
On 8/16/2018 5:35 PM, Marko Kovacevic wrote:
> Fixed formatting an extra header was added making it an extra
> section when it was not intended.
>
> Fixes: d0dff9ba445e ("doc: sample application user guide")
> Cc: bernard.iremonger@intel.com
>
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: stable@dpdk.org
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-10-16 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 16:35 [PATCH v1] doc: fix sample application formatting Marko Kovacevic
2018-10-16 15:08 ` Ferruh Yigit [this message]
2018-11-19 0:27 ` Thomas Monjalon
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=6db5b5b0-2d82-6292-22f1-bb088e9e9dd4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@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