automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Srikanth Yalavarthi <syalavarthi@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw133388-133421 [PATCH v9 01/34] ml/cnxk: drop support for register polling
Date: Thu, 26 Oct 2023 20:31:27 +0800	[thread overview]
Message-ID: <202310261231.39QCVR0I096210@localhost.localdomain> (raw)
In-Reply-To: <20231026124347.22477-2-syalavarthi@marvell.com>

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

_apply patch failure_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Thu, 26 Oct 2023 05:43:10 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 656dfad43136ef43f4315ab6ed45b78b68c287a7

Apply patch set 133388-133421 failed:

Checking patch config/arm/arm64_cn10k_linux_gcc...
Checking patch config/arm/arm64_cn9k_linux_gcc...
Checking patch doc/guides/mldevs/cnxk.rst...
Checking patch drivers/ml/cnxk/cnxk_ml_ops.c...
Checking patch drivers/ml/cnxk/cnxk_ml_ops.h...
Checking patch drivers/ml/cnxk/meson.build...
error: while searching for:
    subdir_done()
endif

sources = files(
        'cn10k_ml_dev.c',
        'cn10k_ml_ops.c',

error: patch failed: drivers/ml/cnxk/meson.build:7
error: drivers/ml/cnxk/meson.build: patch does not apply
Checking patch drivers/ml/cnxk/mvtvm_ml_ops.c...
Checking patch drivers/ml/cnxk/mvtvm_ml_ops.h...
Checking patch drivers/ml/cnxk/mvtvm_ml_stubs.c...
Checking patch drivers/ml/cnxk/mvtvm_ml_stubs.h...


       reply	other threads:[~2023-10-26 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231026124347.22477-2-syalavarthi@marvell.com>
2023-10-26 12:31 ` qemudev [this message]
2023-10-26 12:46 ` |SUCCESS| pw133388 " checkpatch

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=202310261231.39QCVR0I096210@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=syalavarthi@marvell.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).