automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Tomasz Duszynski <tduszynski@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw145528-145531 [PATCH v13 1/4] lib: add generic support for reading PMU events
Date: Wed, 9 Oct 2024 18:56:27 +0800	[thread overview]
Message-ID: <202410091056.499AuRWe827605@localhost.localdomain> (raw)
In-Reply-To: <20241009112308.2973903-2-tduszynski@marvell.com>

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

_apply patch failure_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Wed, 9 Oct 2024 13:23:05 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: f6f2307931c90d924405ea44b0b4be9d3d01bd17

Apply patch set 145528-145531 failed:

Checking patch MAINTAINERS...
Hunk #1 succeeded at 1810 (offset -1 lines).
Checking patch app/test/meson.build...
Checking patch app/test/test_pmu.c...
Checking patch doc/api/doxy-api-index.md...
Checking patch doc/api/doxy-api.conf.in...
Checking patch doc/guides/prog_guide/profile_app.rst...
Checking patch doc/guides/rel_notes/release_24_11.rst...
error: while searching for:
  * Added SR-IOV VF support.
  * Added recent 1400/14000 and 15000 models to the supported list.


Removed Items
-------------

error: patch failed: doc/guides/rel_notes/release_24_11.rst:74
error: doc/guides/rel_notes/release_24_11.rst: patch does not apply
Checking patch lib/meson.build...
Checking patch lib/pmu/meson.build...
Checking patch lib/pmu/pmu_private.h...
Checking patch lib/pmu/rte_pmu.c...
Checking patch lib/pmu/rte_pmu.h...
Checking patch lib/pmu/version.map...


       reply	other threads:[~2024-10-09 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241009112308.2973903-2-tduszynski@marvell.com>
2024-10-09 10:56 ` qemudev [this message]
2024-10-09 11:24 ` |WARNING| pw145528 " 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=202410091056.499AuRWe827605@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=tduszynski@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).