automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw125219 [PATCH v1] bus/ifpga: fix issue of accessing null address
Date: Fri, 17 Mar 2023 02:45:11 +0100 (CET)	[thread overview]
Message-ID: <20230317014511.424691209C6@dpdk.org> (raw)
In-Reply-To: <20230316204412.338823-1-wei.huang@intel.com>

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/125219

_coding style OK_



       reply	other threads:[~2023-03-17  1:45 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230316204412.338823-1-wei.huang@intel.com>
2023-03-17  1:45 ` checkpatch [this message]
2023-03-17  1:56 ` qemudev
2023-03-17  2:00 ` qemudev
2023-03-17  4:01 |SUCCESS| pw125219 [PATCH] [v1] " dpdklab
2023-03-17  4:13 dpdklab
2023-03-17  4:14 dpdklab
2023-03-17  4:16 dpdklab
2023-03-17  4:22 dpdklab
2023-03-17  4:25 dpdklab
2023-03-17  4:26 dpdklab
2023-03-17  4:47 dpdklab
2023-03-17  4:55 dpdklab
2023-03-17  4:59 dpdklab
2023-03-17  5:05 dpdklab
2023-03-17  5:10 dpdklab
2023-03-17  5:15 dpdklab
2023-03-17  5:26 dpdklab
2023-03-17  5:29 dpdklab
2023-03-17  5:39 dpdklab
2023-03-17  5:51 dpdklab
2023-03-17  6:08 dpdklab
2023-03-17  6:10 dpdklab
2023-03-17  6:35 dpdklab
2023-03-17  7:16 dpdklab
2023-03-17  7:28 dpdklab
2023-03-17  7:49 dpdklab
2023-03-17  8:01 dpdklab
2023-03-17  9:10 dpdklab
2023-03-17  9:20 dpdklab
2023-03-17 14:31 dpdklab
2023-03-17 14:54 dpdklab
2023-03-19  7:03 dpdklab
2023-03-19  7:22 dpdklab
2023-03-19 13:40 dpdklab
2023-03-19 14:23 dpdklab
2023-03-20  0:39 dpdklab
2023-03-20  1:37 dpdklab
2023-03-20  1:49 dpdklab
2023-03-20  1:59 dpdklab
2023-03-20  2:02 dpdklab
2023-03-20  2:03 dpdklab
2023-03-20  2:08 dpdklab
2023-03-20  2:11 dpdklab
2023-03-20  2:17 dpdklab
2023-03-20  2:21 dpdklab
2023-03-20  2:25 dpdklab
2023-03-20  2:26 dpdklab
2023-03-20  2:30 dpdklab
2023-03-20  2:36 dpdklab
2023-03-20  2:36 dpdklab
2023-03-20 18:54 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=20230317014511.424691209C6@dpdk.org \
    --to=checkpatch@dpdk.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).