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| pw123581 [PATCH v2] eal: cleanup alarm and multiprocess hotplug before memory detach
Date: Thu,  9 Feb 2023 09:19:20 -0500	[thread overview]
Message-ID: <20230209141920.3316871-1-robot@bytheb.org> (raw)
In-Reply-To: <20230209124543.83652-1-changfengnan@bytedance.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-02-09 14:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230209124543.83652-1-changfengnan@bytedance.com>
2023-02-09 12:37 ` qemudev
2023-02-09 12:40 ` qemudev
2023-02-09 12:47 ` |WARNING| " checkpatch
2023-02-09 14:19 ` 0-day Robot [this message]
2023-02-17 10:52 |SUCCESS| pw123581 [PATCH] [v2] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-12 20:55 dpdklab
2023-02-12 15:22 dpdklab
2023-02-11  0:26 dpdklab
2023-02-11  0:26 dpdklab
2023-02-11  0:23 dpdklab
2023-02-11  0:18 dpdklab
2023-02-11  0:16 dpdklab
2023-02-11  0:14 dpdklab
2023-02-10 23:56 dpdklab
2023-02-10 23:56 dpdklab
2023-02-10 23:54 dpdklab
2023-02-10 23:54 dpdklab
2023-02-10 23:52 dpdklab
2023-02-10 23:51 dpdklab
2023-02-10 23:25 dpdklab
2023-02-09 16:36 dpdklab
2023-02-09 13:51 dpdklab
2023-02-09 13:45 dpdklab
2023-02-09 13:38 dpdklab
2023-02-09 13:38 dpdklab
2023-02-09 13:36 dpdklab
2023-02-09 13:34 dpdklab
2023-02-09 13:31 dpdklab
2023-02-09 13:28 dpdklab
2023-02-09 13:26 dpdklab
2023-02-09 13:26 dpdklab
2023-02-09 13:25 dpdklab
2023-02-09 13:22 dpdklab
2023-02-09 13:21 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=20230209141920.3316871-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).