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| pw105880 [PATCH v4] eal: fix unaligned loads/stores in rte_memcpy_generic
Date: Sun, 16 Jan 2022 17:07:08 -0500	[thread overview]
Message-ID: <20220116220708.28067-1-robot@bytheb.org> (raw)
In-Reply-To: <20220116203312.6405-1-lucp.at.work@gmail.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2022-01-16 21:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220116203312.6405-1-lucp.at.work@gmail.com>
2022-01-16 20:36 ` checkpatch
2022-01-16 22:07 ` 0-day Robot [this message]
2022-01-16 22:17 |SUCCESS| pw105880 [PATCH] [v4] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-01-16 21:53 dpdklab
2022-01-16 21:45 dpdklab
2022-01-16 21:42 dpdklab
2022-01-16 21:21 dpdklab
2022-01-16 21:17 dpdklab
2022-01-16 21:12 dpdklab
2022-01-16 21:11 dpdklab
2022-01-16 21:10 dpdklab
2022-01-16 21:05 dpdklab
2022-01-16 21:03 dpdklab
2022-01-16 21:00 dpdklab
2022-01-16 20:58 dpdklab
2022-01-16 20:57 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=20220116220708.28067-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).