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| pw125036 [PATCH] mldev: remove variable self assignment in dev init
Date: Sat, 11 Mar 2023 12:39:17 -0500	[thread overview]
Message-ID: <20230311173917.1719066-1-robot@bytheb.org> (raw)
In-Reply-To: <20230311145705.9178-1-syalavarthi@marvell.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-03-11 16:39 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230311145705.9178-1-syalavarthi@marvell.com>
2023-03-11 14:47 ` qemudev
2023-03-11 14:51 ` qemudev
2023-03-11 14:58 ` checkpatch
2023-03-11 17:39 ` 0-day Robot [this message]
2023-03-11 16:14 dpdklab
2023-03-11 16:16 dpdklab
2023-03-11 16:19 dpdklab
2023-03-11 16:19 dpdklab
2023-03-11 16:26 dpdklab
2023-03-11 16:28 dpdklab
2023-03-11 16:30 dpdklab
2023-03-11 16:31 dpdklab
2023-03-11 16:32 dpdklab
2023-03-11 16:32 dpdklab
2023-03-11 16:35 dpdklab
2023-03-11 16:40 dpdklab
2023-03-11 16:45 dpdklab
2023-03-11 16:46 dpdklab
2023-03-11 16:47 dpdklab
2023-03-11 16:52 dpdklab
2023-03-11 16:54 dpdklab
2023-03-11 16:56 dpdklab
2023-03-11 16:56 dpdklab
2023-03-11 16:59 dpdklab
2023-03-11 17:02 dpdklab
2023-03-11 17:05 dpdklab
2023-03-11 17:06 dpdklab
2023-03-11 17:06 dpdklab
2023-03-11 17:11 dpdklab
2023-03-11 17:17 dpdklab
2023-03-11 17:31 dpdklab
2023-03-11 17:52 dpdklab
2023-03-12 11:10 dpdklab
2023-03-12 11:16 dpdklab
2023-03-12 11:22 dpdklab
2023-03-12 12:00 dpdklab
2023-03-12 20:25 dpdklab
2023-03-12 20:50 dpdklab
2023-03-12 20:56 dpdklab
2023-03-12 20:57 dpdklab
2023-03-12 20:59 dpdklab
2023-03-12 21:00 dpdklab
2023-03-12 21:04 dpdklab
2023-03-12 21:06 dpdklab
2023-03-12 21:19 dpdklab
2023-03-12 21:20 dpdklab
2023-03-12 21:25 dpdklab
2023-03-12 21:27 dpdklab
2023-03-12 21:41 dpdklab
2023-03-12 21:57 dpdklab
2023-03-12 21:58 dpdklab
2023-03-12 22:06 dpdklab
2023-03-12 22:06 dpdklab
2023-03-12 22:08 dpdklab
2023-03-12 22:13 dpdklab
2023-03-12 22:14 dpdklab
2023-03-12 22:16 dpdklab
2023-03-12 22:20 dpdklab
2023-03-12 22:22 dpdklab
2023-03-12 22:24 dpdklab
2023-03-12 22:31 dpdklab
2023-03-12 22:33 dpdklab
2023-03-12 23:21 dpdklab
2023-03-12 23:22 dpdklab
2023-03-13 14:03 dpdklab
2023-03-13 15:30 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=20230311173917.1719066-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).