From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw132689 [PATCH] net/cpfl: fix memory leak
Date: Mon, 16 Oct 2023 23:39:23 -0400 [thread overview]
Message-ID: <20231017033923.2399703-1-robot@bytheb.org> (raw)
In-Reply-To: <20231017110655.582873-1-beilei.xing@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/132689/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/6541970828
next prev parent reply other threads:[~2023-10-17 3:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231017110655.582873-1-beilei.xing@intel.com>
2023-10-17 2:27 ` qemudev
2023-10-17 2:31 ` qemudev
2023-10-17 2:47 ` checkpatch
2023-10-17 3:39 ` 0-day Robot [this message]
2023-10-17 8:17 dpdklab
2023-10-17 8:20 dpdklab
2023-10-17 8:20 dpdklab
2023-10-17 8:21 dpdklab
2023-10-17 8:34 dpdklab
2023-10-17 8:41 dpdklab
2023-10-17 8:41 dpdklab
2023-10-17 8:42 dpdklab
2023-10-17 8:50 dpdklab
2023-10-17 8:50 dpdklab
2023-10-17 8:51 dpdklab
2023-10-17 8:51 dpdklab
2023-10-17 8:52 dpdklab
2023-10-17 8:57 dpdklab
2023-10-17 8:58 dpdklab
2023-10-17 8:58 dpdklab
2023-10-17 8:59 dpdklab
2023-10-17 9:00 dpdklab
2023-10-17 9:00 dpdklab
2023-10-17 9:01 dpdklab
2023-10-17 9:02 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:03 dpdklab
2023-10-17 9:04 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:07 dpdklab
2023-10-17 9:20 dpdklab
2023-10-17 9:26 dpdklab
2023-10-17 9:38 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:41 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:42 dpdklab
2023-10-17 9:45 dpdklab
2023-10-17 9:49 dpdklab
2023-10-17 9:49 dpdklab
2023-10-17 9:58 dpdklab
2023-10-17 10:09 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 21:49 dpdklab
2023-10-18 20:13 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=20231017033923.2399703-1-robot@bytheb.org \
--to=robot@bytheb.org \
--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).