From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw125033 [PATCH] ml/cnxk: fix updating error code and message
Date: Sat, 11 Mar 2023 12:51:38 +0100 (CET) [thread overview]
Message-ID: <20230311115138.80C171209BE@dpdk.org> (raw)
In-Reply-To: <20230311115045.23320-1-syalavarthi@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/125033
_coding style OK_
next prev parent reply other threads:[~2023-03-11 11:51 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230311115045.23320-1-syalavarthi@marvell.com>
2023-03-11 11:40 ` qemudev
2023-03-11 11:43 ` qemudev
2023-03-11 11:51 ` checkpatch [this message]
2023-03-11 14:19 ` 0-day Robot
2023-03-13 12:44 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 11:24 dpdklab
2023-03-12 20:53 dpdklab
2023-03-12 20:53 dpdklab
2023-03-12 20:50 dpdklab
2023-03-12 20:44 dpdklab
2023-03-12 20:42 dpdklab
2023-03-12 20:40 dpdklab
2023-03-12 20:32 dpdklab
2023-03-12 20:26 dpdklab
2023-03-12 20:23 dpdklab
2023-03-12 19:58 dpdklab
2023-03-12 19:58 dpdklab
2023-03-12 19:53 dpdklab
2023-03-12 19:52 dpdklab
2023-03-12 19:48 dpdklab
2023-03-12 19:47 dpdklab
2023-03-12 19:41 dpdklab
2023-03-12 19:22 dpdklab
2023-03-12 19:20 dpdklab
2023-03-12 19:20 dpdklab
2023-03-12 19:18 dpdklab
2023-03-12 19:16 dpdklab
2023-03-12 19:15 dpdklab
2023-03-12 19:14 dpdklab
2023-03-12 19:08 dpdklab
2023-03-12 19:05 dpdklab
2023-03-12 19:02 dpdklab
2023-03-12 18:47 dpdklab
2023-03-12 18:40 dpdklab
2023-03-12 10:56 dpdklab
2023-03-12 9:46 dpdklab
2023-03-12 9:45 dpdklab
2023-03-12 8:56 dpdklab
2023-03-11 14:57 dpdklab
2023-03-11 13:52 dpdklab
2023-03-11 13:48 dpdklab
2023-03-11 13:43 dpdklab
2023-03-11 13:41 dpdklab
2023-03-11 13:40 dpdklab
2023-03-11 13:39 dpdklab
2023-03-11 13:38 dpdklab
2023-03-11 13:38 dpdklab
2023-03-11 13:35 dpdklab
2023-03-11 13:34 dpdklab
2023-03-11 13:33 dpdklab
2023-03-11 13:31 dpdklab
2023-03-11 13:28 dpdklab
2023-03-11 13:21 dpdklab
2023-03-11 13:02 dpdklab
2023-03-11 12:58 dpdklab
2023-03-11 12:53 dpdklab
2023-03-11 12:51 dpdklab
2023-03-11 12:50 dpdklab
2023-03-11 12:50 dpdklab
2023-03-11 12:48 dpdklab
2023-03-11 12:44 dpdklab
2023-03-11 12:44 dpdklab
2023-03-11 12:42 dpdklab
2023-03-11 12:42 dpdklab
2023-03-11 12:41 dpdklab
2023-03-11 12:34 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=20230311115138.80C171209BE@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).