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| pw123486 [PATCH v2] mailmap: update mailmap entry for second address
Date: Wed,  8 Feb 2023 17:39:48 -0500	[thread overview]
Message-ID: <20230208223948.3850248-1-robot@bytheb.org> (raw)
In-Reply-To: <1675893354-1267-1-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-02-08 22:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1675893354-1267-1-git-send-email-roretzla@linux.microsoft.com>
2023-02-08 21:47 ` qemudev
2023-02-08 21:50 ` qemudev
2023-02-08 21:56 ` |WARNING| " checkpatch
2023-02-08 22:39 ` 0-day Robot [this message]
2023-02-08 22:21 |SUCCESS| pw123486 [PATCH] [v2] " dpdklab
2023-02-08 22:27 dpdklab
2023-02-08 22:31 dpdklab
2023-02-08 22:31 dpdklab
2023-02-08 22:31 dpdklab
2023-02-08 22:36 dpdklab
2023-02-08 22:37 dpdklab
2023-02-08 22:42 dpdklab
2023-02-08 22:45 dpdklab
2023-02-08 22:45 dpdklab
2023-02-08 22:46 dpdklab
2023-02-08 22:52 dpdklab
2023-02-08 23:05 dpdklab
2023-02-09  0:08 dpdklab
2023-02-10  2:17 dpdklab
2023-02-10  2:31 dpdklab
2023-02-10  2:36 dpdklab
2023-02-10  2:37 dpdklab
2023-02-10  2:40 dpdklab
2023-02-10  2:42 dpdklab
2023-02-10  2:48 dpdklab
2023-02-10  2:49 dpdklab
2023-02-10  2:54 dpdklab
2023-02-10  3:02 dpdklab
2023-02-10  3:06 dpdklab
2023-02-10  3:12 dpdklab
2023-02-10  3:14 dpdklab
2023-02-10  3:14 dpdklab
2023-02-11  8:10 dpdklab
2023-02-11 18:53 dpdklab
2023-02-12  0:40 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=20230208223948.3850248-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).