automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: "Warrington, Jeffrey" <jwarrington@verisign.com>, zhoumin@loongson.cn
Subject: |WARNING| pw133934 [PATCH] lpm: improve performance with copious IPv4 peering routes
Date: Tue, 7 Nov 2023 20:29:32 +0800	[thread overview]
Message-ID: <202311071229.3A7CTWRp1362643@localhost.localdomain> (raw)
In-Reply-To: <A140CF70-E99E-4DAA-8A14-B3FB19B0A529@verisign.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/133934

_apply patch failure_

Submitter: Warrington, Jeffrey <jwarrington@verisign.com>
Date: Tue, 7 Nov 2023 12:49:13 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2bbad8f974e00552d106c27e1d157a31179ab5ec

Apply patch set 133934 failed:

error: corrupt patch at line 103


       reply	other threads:[~2023-11-07 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A140CF70-E99E-4DAA-8A14-B3FB19B0A529@verisign.com>
2023-11-07 12:29 ` qemudev [this message]
2023-11-07 12:49 ` checkpatch
2023-11-07 15:21 dpdklab

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=202311071229.3A7CTWRp1362643@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=jwarrington@verisign.com \
    --cc=test-report@dpdk.org \
    --cc=zhoumin@loongson.cn \
    /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).