From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw105924 [PATCH] net/cnxk: fix dangling pointer in meter for gcc12
Date: Mon, 17 Jan 2022 10:40:04 -0500 [thread overview]
Message-ID: <20220117154004.28665-1-robot@bytheb.org> (raw)
In-Reply-To: <20220117140226.3019392-1-ferruh.yigit@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/105924/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1708403100
next prev parent reply other threads:[~2022-01-17 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220117140226.3019392-1-ferruh.yigit@intel.com>
2022-01-17 14:06 ` |WARNING| " checkpatch
2022-01-17 15:40 ` 0-day Robot [this message]
2022-01-17 14:46 |SUCCESS| " dpdklab
2022-01-17 14:57 dpdklab
2022-01-17 14:58 dpdklab
2022-01-17 15:00 dpdklab
2022-01-17 15:05 dpdklab
2022-01-17 15:09 dpdklab
2022-01-17 15:12 dpdklab
2022-01-17 16:14 dpdklab
2022-01-17 16:27 dpdklab
2022-01-17 16:44 dpdklab
2022-01-17 17:11 dpdklab
2022-01-17 17:34 dpdklab
2022-01-17 18:44 dpdklab
2022-01-17 21:53 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=20220117154004.28665-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).