automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140913 [PATCH] net/mana: fix uninitialized scalar variable
Date: Mon, 10 Jun 2024 18:44:06 -0400	[thread overview]
Message-ID: <20240610224406.3033148-1-robot@bytheb.org> (raw)
In-Reply-To: <20240610214320.676239-1-mahmoudmatook.mm@gmail.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140913/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9456202872

  parent reply	other threads:[~2024-06-10 22:44 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240610214320.676239-1-mahmoudmatook.mm@gmail.com>
2024-06-10 21:20 ` qemudev
2024-06-10 21:24 ` qemudev
2024-06-10 21:44 ` |WARNING| " checkpatch
2024-06-10 22:44 ` 0-day Robot [this message]
2024-06-10 23:21 ` |SUCCESS| pw140913 [PATCH] net/mana: fix uninitialized scalar variab dpdklab
2024-06-10 23:22 ` dpdklab
2024-06-10 23:23 ` dpdklab
2024-06-10 23:33 ` dpdklab
2024-06-10 23:36 ` dpdklab
2024-06-10 23:58 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:18 ` dpdklab
2024-06-12 23:18 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:34 ` dpdklab
2024-06-12 23:36 ` 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=20240610224406.3033148-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).