From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Mike Bly <bly454@gmail.com>, zhoumin@loongson.cn
Subject: |WARNING| pw149661 [PATCH] net/memif: Fix memif-rx buffer linking
Date: Tue, 7 Jan 2025 17:29:10 +0800 [thread overview]
Message-ID: <202501070929.5079TAtN2901968@localhost.localdomain> (raw)
In-Reply-To: <CAB3eHOy3KS1LX3=7Vdy5aJ2V-0iGSHxXEFcRsHHWvO2LbZNKPg@mail.gmail.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/149661
_apply patch failure_
Submitter: Mike Bly <bly454@gmail.com>
Date: Mon, 6 Jan 2025 11:43:28 -0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 94ad302b4ebba4a5b6706a1c43ea0505e5098169
Apply patch set 149661 failed:
error: git diff header lacks filename information when removing 1 leading pathname component (line 92)
next parent reply other threads:[~2025-01-07 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB3eHOy3KS1LX3=7Vdy5aJ2V-0iGSHxXEFcRsHHWvO2LbZNKPg@mail.gmail.com>
2025-01-07 9:29 ` qemudev [this message]
2025-01-07 9:59 ` 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=202501070929.5079TAtN2901968@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=bly454@gmail.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).