automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw139994 [PATCH] eal/unix: support ZSTD compression for firmwares
Date: Wed,  8 May 2024 11:53:59 +0200 (CEST)	[thread overview]
Message-ID: <20240508095359.7E7EF121E57@dpdk.org> (raw)
In-Reply-To: <20240508095214.2541115-1-david.marchand@redhat.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139994

_coding style issues_


WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#90: FILE: lib/eal/unix/eal_firmware.c:22:
+extern int archive_read_support_filter_xz(struct archive *a);

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#91: FILE: lib/eal/unix/eal_firmware.c:23:
+extern int archive_read_support_filter_zstd(struct archive *a);

total: 0 errors, 2 warnings, 71 lines checked

  parent reply	other threads:[~2024-05-08  9:54 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240508095214.2541115-1-david.marchand@redhat.com>
2024-05-08  9:26 ` |SUCCESS| " qemudev
2024-05-08  9:31 ` qemudev
2024-05-08  9:53 ` checkpatch [this message]
2024-05-08 10:44 ` 0-day Robot
2024-05-08 12:07 ` |SUCCESS| pw139994 [PATCH] eal/unix: support ZSTD compression for fi dpdklab
2024-05-08 12:09 ` dpdklab
2024-05-08 12:10 ` dpdklab
2024-05-08 12:11 ` dpdklab
2024-05-08 12:11 ` dpdklab
2024-05-08 12:19 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:48 ` dpdklab
2024-05-08 12:49 ` dpdklab
2024-05-08 12:50 ` dpdklab
2024-05-08 12:51 ` dpdklab
2024-05-08 12:51 ` dpdklab
2024-05-08 12:52 ` dpdklab
2024-05-08 12:53 ` dpdklab
2024-05-08 12:54 ` dpdklab
2024-05-08 12:55 ` dpdklab
2024-05-08 12:55 ` dpdklab
2024-05-08 12:57 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 13:00 ` dpdklab
2024-05-08 13:03 ` dpdklab
2024-05-08 13:06 ` dpdklab
2024-05-08 13:07 ` dpdklab
2024-05-08 13:15 ` dpdklab
2024-05-08 13:22 ` dpdklab
2024-05-08 13:45 ` dpdklab
2024-05-08 13:51 ` dpdklab
2024-05-08 13:53 ` 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=20240508095359.7E7EF121E57@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=david.marchand@redhat.com \
    --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).