automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: arybchenko@solarflare.com, test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw17417  [PATCH, 31/31] net/sfc: support firmware-assisted TSOv2
Date: 02 Dec 2016 02:26:35 -0800	[thread overview]
Message-ID: <6f050a$102l4r6@fmsmga001.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 15069 bytes --]

Test-Label: Intel Per-patch compilation check
Test-Status: FAILURE

Patchwork ID: 17417
http://www.dpdk.org/dev/patchwork/patch/17417
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Fri, 2 Dec 2016 07:44:42 +0000
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:e6c7b6ec57f3527ce55fa3e0d2a8ed1533722253
                   Repo:dpdk-next-net, Branch:master, CommitID:f6a3c2dcd9ca29613a84d28f3cb07521b0d37ea3
                   Repo:dpdk-next-virtio, Branch:master, CommitID:b5415fbc69dd33a1bb64a140b2f6bc73d11e4d22
                   Repo:dpdk, Branch:master, CommitID:112fc39b829039ee4ade210c464d26fecde7eac0
                   
Apply patch file failed:
Repo: dpdk-next-crypto
17417:
patching file config/common_base
Hunk #1 FAILED at 342.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/sfc_efx.ini b/doc/guides/nics/features/sfc_efx.ini
|index 07c58d5..3a15baa 100644
|--- a/doc/guides/nics/features/sfc_efx.ini
|+++ b/doc/guides/nics/features/sfc_efx.ini
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 62
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
|index 64489de..f826726 100644
|--- a/doc/guides/nics/sfc_efx.rst
|+++ b/doc/guides/nics/sfc_efx.rst
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/Makefile b/drivers/net/sfc/Makefile
|index dd099b2..14d6536 100644
|--- a/drivers/net/sfc/Makefile
|+++ b/drivers/net/sfc/Makefile
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 108
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.c b/drivers/net/sfc/sfc.c
|index e79367d..02a56f7 100644
|--- a/drivers/net/sfc/sfc.c
|+++ b/drivers/net/sfc/sfc.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 127
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.h b/drivers/net/sfc/sfc.h
|index 01dbfb6..df9c20b 100644
|--- a/drivers/net/sfc/sfc.h
|+++ b/drivers/net/sfc/sfc.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 140
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_ethdev.c b/drivers/net/sfc/sfc_ethdev.c
|index 09cc46b..1fb763a 100644
|--- a/drivers/net/sfc/sfc_ethdev.c
|+++ b/drivers/net/sfc/sfc_ethdev.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/sfc/sfc_tso.c
can't find file to patch at input line 363
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.c b/drivers/net/sfc/sfc_tx.c
|index 86bcfec..cb21f78 100644
|--- a/drivers/net/sfc/sfc_tx.c
|+++ b/drivers/net/sfc/sfc_tx.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 526
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.h b/drivers/net/sfc/sfc_tx.h
|index 4d25c6a..d4298e4 100644
|--- a/drivers/net/sfc/sfc_tx.h
|+++ b/drivers/net/sfc/sfc_tx.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored

Repo: dpdk-next-net
17417:
patching file config/common_base
Hunk #1 FAILED at 342.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/sfc_efx.ini b/doc/guides/nics/features/sfc_efx.ini
|index 07c58d5..3a15baa 100644
|--- a/doc/guides/nics/features/sfc_efx.ini
|+++ b/doc/guides/nics/features/sfc_efx.ini
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 62
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
|index 64489de..f826726 100644
|--- a/doc/guides/nics/sfc_efx.rst
|+++ b/doc/guides/nics/sfc_efx.rst
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/Makefile b/drivers/net/sfc/Makefile
|index dd099b2..14d6536 100644
|--- a/drivers/net/sfc/Makefile
|+++ b/drivers/net/sfc/Makefile
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 108
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.c b/drivers/net/sfc/sfc.c
|index e79367d..02a56f7 100644
|--- a/drivers/net/sfc/sfc.c
|+++ b/drivers/net/sfc/sfc.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 127
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.h b/drivers/net/sfc/sfc.h
|index 01dbfb6..df9c20b 100644
|--- a/drivers/net/sfc/sfc.h
|+++ b/drivers/net/sfc/sfc.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 140
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_ethdev.c b/drivers/net/sfc/sfc_ethdev.c
|index 09cc46b..1fb763a 100644
|--- a/drivers/net/sfc/sfc_ethdev.c
|+++ b/drivers/net/sfc/sfc_ethdev.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/sfc/sfc_tso.c
can't find file to patch at input line 363
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.c b/drivers/net/sfc/sfc_tx.c
|index 86bcfec..cb21f78 100644
|--- a/drivers/net/sfc/sfc_tx.c
|+++ b/drivers/net/sfc/sfc_tx.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 526
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.h b/drivers/net/sfc/sfc_tx.h
|index 4d25c6a..d4298e4 100644
|--- a/drivers/net/sfc/sfc_tx.h
|+++ b/drivers/net/sfc/sfc_tx.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored

Repo: dpdk-next-virtio
17417:
patching file config/common_base
Hunk #1 FAILED at 342.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/sfc_efx.ini b/doc/guides/nics/features/sfc_efx.ini
|index 07c58d5..3a15baa 100644
|--- a/doc/guides/nics/features/sfc_efx.ini
|+++ b/doc/guides/nics/features/sfc_efx.ini
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 62
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
|index 64489de..f826726 100644
|--- a/doc/guides/nics/sfc_efx.rst
|+++ b/doc/guides/nics/sfc_efx.rst
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/Makefile b/drivers/net/sfc/Makefile
|index dd099b2..14d6536 100644
|--- a/drivers/net/sfc/Makefile
|+++ b/drivers/net/sfc/Makefile
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 108
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.c b/drivers/net/sfc/sfc.c
|index e79367d..02a56f7 100644
|--- a/drivers/net/sfc/sfc.c
|+++ b/drivers/net/sfc/sfc.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 127
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.h b/drivers/net/sfc/sfc.h
|index 01dbfb6..df9c20b 100644
|--- a/drivers/net/sfc/sfc.h
|+++ b/drivers/net/sfc/sfc.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 140
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_ethdev.c b/drivers/net/sfc/sfc_ethdev.c
|index 09cc46b..1fb763a 100644
|--- a/drivers/net/sfc/sfc_ethdev.c
|+++ b/drivers/net/sfc/sfc_ethdev.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/sfc/sfc_tso.c
can't find file to patch at input line 363
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.c b/drivers/net/sfc/sfc_tx.c
|index 86bcfec..cb21f78 100644
|--- a/drivers/net/sfc/sfc_tx.c
|+++ b/drivers/net/sfc/sfc_tx.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 526
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.h b/drivers/net/sfc/sfc_tx.h
|index 4d25c6a..d4298e4 100644
|--- a/drivers/net/sfc/sfc_tx.h
|+++ b/drivers/net/sfc/sfc_tx.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored

Repo: dpdk
17417:
patching file config/common_base
Hunk #1 FAILED at 342.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/sfc_efx.ini b/doc/guides/nics/features/sfc_efx.ini
|index 07c58d5..3a15baa 100644
|--- a/doc/guides/nics/features/sfc_efx.ini
|+++ b/doc/guides/nics/features/sfc_efx.ini
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 62
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
|index 64489de..f826726 100644
|--- a/doc/guides/nics/sfc_efx.rst
|+++ b/doc/guides/nics/sfc_efx.rst
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/Makefile b/drivers/net/sfc/Makefile
|index dd099b2..14d6536 100644
|--- a/drivers/net/sfc/Makefile
|+++ b/drivers/net/sfc/Makefile
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 108
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.c b/drivers/net/sfc/sfc.c
|index e79367d..02a56f7 100644
|--- a/drivers/net/sfc/sfc.c
|+++ b/drivers/net/sfc/sfc.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 127
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc.h b/drivers/net/sfc/sfc.h
|index 01dbfb6..df9c20b 100644
|--- a/drivers/net/sfc/sfc.h
|+++ b/drivers/net/sfc/sfc.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 140
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_ethdev.c b/drivers/net/sfc/sfc_ethdev.c
|index 09cc46b..1fb763a 100644
|--- a/drivers/net/sfc/sfc_ethdev.c
|+++ b/drivers/net/sfc/sfc_ethdev.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/sfc/sfc_tso.c
can't find file to patch at input line 363
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.c b/drivers/net/sfc/sfc_tx.c
|index 86bcfec..cb21f78 100644
|--- a/drivers/net/sfc/sfc_tx.c
|+++ b/drivers/net/sfc/sfc_tx.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
9 out of 9 hunks ignored
can't find file to patch at input line 526
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/sfc/sfc_tx.h b/drivers/net/sfc/sfc_tx.h
|index 4d25c6a..d4298e4 100644
|--- a/drivers/net/sfc/sfc_tx.h
|+++ b/drivers/net/sfc/sfc_tx.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored


DPDK STV team

                 reply	other threads:[~2016-12-02 10:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='6f050a$102l4r6@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=test-report@dpdk.org \
    /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).