From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: ip_pipeline app user guide
Date: Tue, 11 Aug 2015 08:12:08 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2022E34E8@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2174685.JxsPPVaeJl@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, August 10, 2015 10:45 PM
> To: Dumitrescu, Cristian
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: ip_pipeline app user guide
>
> 2015-08-06 14:48, Cristian Dumitrescu:
> > Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ...
>
> The patch is corrupted.
> Checkpatch reports:
> ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?) Git
> reports:
> fatal: corrupt patch at line 191
Hi,
I think the problem is that the svg files had lines over 1000 chars that got truncated by git-send-patch or the mailer daemon.
We'll resubmit the patchset.
John
next prev parent reply other threads:[~2015-08-11 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 13:48 Cristian Dumitrescu
2015-08-06 13:55 ` Singh, Jasvinder
2015-08-06 14:38 ` Azarewicz, PiotrX T
2015-08-07 15:44 ` Mcnamara, John
2015-08-10 21:44 ` Thomas Monjalon
2015-08-11 8:12 ` Mcnamara, John [this message]
2015-08-11 16:47 ` [dpdk-dev] [PATCH v2] " John McNamara
2015-08-11 17:23 ` Dumitrescu, Cristian
2015-08-11 20:37 ` Thomas Monjalon
2015-08-11 20:46 ` Dumitrescu, Cristian
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=B27915DBBA3421428155699D51E4CFE2022E34E8@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).