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 10:16:44 +0100 [thread overview]
Message-ID: <4375123.HCZRrftiMy@xps> (raw)
In-Reply-To: <20191029131942.50298-1-jasvinder.singh@intel.com>
29/10/2019 14:19, Jasvinder Singh:
> diff --git a/doc/guides/prog_guide/img/sched_hier_per_port.svg b/doc/guides/prog_guide/img/sched_hier_per_port.svg
> new file mode 100644
> index 0000000000000000000000000000000000000000..d77ee70a2dd06eedc2c10f44621902921a820806
> GIT binary patch
I missed it.
This is not a SVG file. I hope it is a mistake.
Please do not send any binary file.
next prev parent reply other threads:[~2019-11-26 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 13:19 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
2019-11-26 9:16 ` Thomas Monjalon [this message]
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=4375123.HCZRrftiMy@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 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).