DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wisam Monther <wisamm@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"wisamm@mellanox.com" <wisamm@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc/flow-perf: fix section headings
Date: Sun, 6 Sep 2020 07:31:48 +0000	[thread overview]
Message-ID: <BL0PR12MB2419435EBEAC471E62E76B70A42B0@BL0PR12MB2419.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200906033952.24895-1-stephen@networkplumber.org>

>-----Original Message-----
>From: Stephen Hemminger <stephen@networkplumber.org>
>Sent: Sunday, September 6, 2020 6:40 AM
>To: john.mcnamara@intel.com; marko.kovacevic@intel.com;
>wisamm@mellanox.com
>Cc: dev@dpdk.org; Stephen Hemminger <stephen@networkplumber.org>
>Subject: [PATCH] doc/flow-perf: fix section headings
>
>The flow-perf documentation was using multiple section headings in one
>document. This caused the documentation tree display in index to make it
>appear as multiple pages rather than sub-sections in one page.
>
>Change to use subsections and subsubsections.
>
>Fixes: bf3688f1e816 ("app/flow-perf: add insertion rate calculation")
>Cc: wisamm@mellanox.com
>Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Hi Stephen,

Thanks for your fix,
I sent a patch with the fix that pending review from a week ago with the same fixes:
http://patches.dpdk.org/patch/76152/

BRs,
Wisam Jaddo

      reply	other threads:[~2020-09-07 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06  3:39 Stephen Hemminger
2020-09-06  7:31 ` Wisam Monther [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=BL0PR12MB2419435EBEAC471E62E76B70A42B0@BL0PR12MB2419.namprd12.prod.outlook.com \
    --to=wisamm@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=wisamm@mellanox.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).