From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com,
john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/3] sched: documentation update
Date: Tue, 26 Nov 2019 09:47:41 +0100 [thread overview]
Message-ID: <3017568.4A7DOBss1a@xps> (raw)
In-Reply-To: <20191029131942.50298-1-jasvinder.singh@intel.com>
29/10/2019 14:19, Jasvinder Singh:
> Updates documentation to reflect the changes in the qos scheduler
> library.
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> ---
> .../prog_guide/img/sched_hier_per_port.png | Bin 58973 -> 0 bytes
> .../prog_guide/img/sched_hier_per_port.svg | Bin 0 -> 1463490 bytes
[...]
> -.. figure:: img/sched_hier_per_port.*
> +.. figure:: img/sched_hier_per_port.svg
checkpatches.sh raises this warning:
Warning in /doc/guides/prog_guide/qos_framework.rst:
Using explicit .svg extension instead of .*
Wildcard is needed because PDF build converts svg to png.
I will fix when applying.
next prev parent reply other threads:[~2019-11-26 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 13:19 [dpdk-dev] [PATCH 1/3] sched: documentation update Jasvinder Singh
2019-10-29 13:19 ` [dpdk-dev] [PATCH 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-04 10:29 ` Dumitrescu, Cristian
2019-10-29 13:19 ` [dpdk-dev] [PATCH 3/3] examples/ip_pipeline: " Jasvinder Singh
2019-11-04 10:29 ` Dumitrescu, Cristian
2019-11-04 10:30 ` [dpdk-dev] [PATCH 1/3] sched: " Dumitrescu, Cristian
2019-11-26 8:47 ` Thomas Monjalon [this message]
2019-11-26 9:16 ` Thomas Monjalon
2019-11-26 9:55 ` Singh, Jasvinder
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 " Jasvinder Singh
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 3/3] examples/ip_pipeline: " Jasvinder Singh
2019-11-26 15:22 ` [dpdk-dev] [PATCH v2 1/3] sched: " 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=3017568.4A7DOBss1a@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.