From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 2/4] doc: remove redundant prerequisite info for dpaa devices
Date: Sun, 16 Sep 2018 01:05:47 +0200 [thread overview]
Message-ID: <1682492.GABOoNfPDe@xps> (raw)
In-Reply-To: <1536305122-23322-2-git-send-email-hemant.agrawal@nxp.com>
07/09/2018 09:25, Hemant Agrawal:
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> doc/guides/cryptodevs/dpaa_sec.rst | 25 ++--------------
> doc/guides/eventdevs/dpaa.rst | 48 +++----------------------------
> doc/guides/nics/dpaa.rst | 59 +-------------------------------------
> 3 files changed, 7 insertions(+), 125 deletions(-)
If I understand well, first patch is copying the content in a new place,
and second patch is removing the original content. It is a move, right?
Would it be clearer to merge patch pairs?
next prev parent reply other threads:[~2018-09-16 8:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 7:39 [dpdk-dev] [PATCH 1/4] doc: create a platorm specific page for NXP DPAA platform Hemant Agrawal
2018-08-30 7:39 ` [dpdk-dev] [PATCH 2/4] doc: remove redundant prerequisite info for dpaa devices Hemant Agrawal
2018-08-30 7:39 ` [dpdk-dev] [PATCH 3/4] doc: create a platorm specific page for NXP DPAA2 platform Hemant Agrawal
2018-08-30 7:39 ` [dpdk-dev] [PATCH 4/4] doc: remove redundant prerequisite info for dpaa2 devices Hemant Agrawal
2018-09-07 7:25 ` [dpdk-dev] [PATCH v2 1/4] doc: create a platorm specific page for NXP DPAA platform Hemant Agrawal
2018-09-07 7:25 ` [dpdk-dev] [PATCH v2 2/4] doc: remove redundant prerequisite info for dpaa devices Hemant Agrawal
2018-09-15 23:05 ` Thomas Monjalon [this message]
2018-09-17 3:22 ` Hemant Agrawal
2018-09-07 7:25 ` [dpdk-dev] [PATCH v2 3/4] doc: create a platorm specific page for NXP DPAA2 platform Hemant Agrawal
2018-09-07 7:25 ` [dpdk-dev] [PATCH v2 4/4] doc: remove redundant prerequisite info for dpaa2 devices Hemant Agrawal
2018-09-18 13:04 ` [dpdk-dev] [PATCH v3 1/2] doc: create a platorm specific page for NXP DPAA platform Hemant Agrawal
2018-09-18 13:04 ` [dpdk-dev] [PATCH v3 2/2] doc: create a platorm specific page for NXP DPAA2 platform Hemant Agrawal
2018-09-25 11:17 ` Kovacevic, Marko
2018-09-25 10:59 ` [dpdk-dev] [PATCH v3 1/2] doc: create a platorm specific page for NXP DPAA platform Kovacevic, Marko
2018-09-26 7:42 ` [dpdk-dev] [PATCH v4 " Hemant Agrawal
2018-09-26 7:42 ` [dpdk-dev] [PATCH v4 2/2] doc: create a platorm specific page for NXP DPAA2 platform Hemant Agrawal
2018-11-19 0:16 ` 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=1682492.GABOoNfPDe@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=john.mcnamara@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).