From: Ferruh Yigit <ferruh.yigit@intel.com>
To: prateekag@cse.iitb.ac.in
Cc: dpdk-dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] Documentation errata:RCU_lib.rst and Ring fig 6.10 corrected
Date: Wed, 29 Jan 2020 16:49:00 +0000 [thread overview]
Message-ID: <392e1994-5afe-cf89-3545-0c92ccaa4dd5@intel.com> (raw)
In-Reply-To: <20200129023133.8547-1-prateekag@cse.iitb.ac.in>
On 1/29/2020 2:31 AM, prateekag@cse.iitb.ac.in wrote:
> From: PRATEEK AGARWAL <prateekag@cse.iitb.ac.in>
>
> ---
> .../prog_guide/img/ring-mp-enqueue3.png | Bin 0 -> 52346 bytes
> .../prog_guide/img/ring-mp-enqueue3.svg | 785 ------------------
> doc/guides/prog_guide/rcu_lib.rst | 2 +-
> 3 files changed, 1 insertion(+), 786 deletions(-)
> create mode 100644 doc/guides/prog_guide/img/ring-mp-enqueue3.png
> delete mode 100644 doc/guides/prog_guide/img/ring-mp-enqueue3.svg
Change is only in .svg file, no need to add and delete .png file, can you please
squash these two patches?
prev parent reply other threads:[~2020-01-29 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 2:31 prateekag
2020-01-29 2:31 ` [dpdk-dev] [PATCH 2/2] 6.10 png replaced with svg prateekag
2020-01-29 16:49 ` Ferruh Yigit [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=392e1994-5afe-cf89-3545-0c92ccaa4dd5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=prateekag@cse.iitb.ac.in \
/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).