From: Patchwork <patchwork@emeril.freedesktop.org>
To: Alastair D'Silva <alastair@au1.ibm.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for Hexdump enhancements
Date: Wed, 10 Apr 2019 17:53:20 -0000 [thread overview]
Message-ID: <20190410175320.19551.64933@emeril.freedesktop.org> (raw)
In-Reply-To: <20190410031720.11067-1-alastair@au1.ibm.com>
== Series Details ==
Series: Hexdump enhancements
URL : https://patchwork.freedesktop.org/series/59296/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4911981b19d1 lib/hexdump.c: Allow 64 bytes per line
49ccc448ceaa lib/hexdump.c: Optionally suppress lines of filler bytes
-:50: CHECK:AVOID_EXTERNS: extern prototypes should be avoided in .h files
#50: FILE: include/linux/printk.h:499:
+extern void print_hex_dump_ext(const char *level, const char *prefix_str,
-:83: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#83: FILE: include/linux/printk.h:529:
+ print_hex_dump_ext(level, prefix_str, prefix_type, rowsize, groupsize,
+ buf, len, ascii ? HEXDUMP_ASCII : 0);
-:86: CHECK:LINE_SPACING: Please don't use multiple blank lines
#86: FILE: include/linux/printk.h:532:
+
+
-:217: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#217: FILE: lib/hexdump.c:338:
+ print_hex_dump_ext(KERN_DEBUG, prefix_str, prefix_type, 16, 1,
+ buf, len, HEXDUMP_ASCII);
total: 0 errors, 0 warnings, 4 checks, 185 lines checked
560d296fb9d8 lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags
-:282: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#282: FILE: lib/test_hexdump.c:175:
+ r = hex_dump_to_buffer(data_b, len, rs, gs, buf, buflen,
+ ascii ? HEXDUMP_ASCII : 0);
total: 0 errors, 0 warnings, 1 checks, 195 lines checked
3470b899c699 lib/hexdump.c: Allow multiple groups to be separated by lines '|'
-:125: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#125: FILE: lib/hexdump.c:232:
+ if (line_chars && ((j + 1) < len) &&
+ ((j + 1) % line_chars == 0)) {
total: 0 errors, 0 warnings, 1 checks, 124 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-10 17:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 3:17 [PATCH 0/4] Hexdump enhancements Alastair D'Silva
2019-04-10 3:17 ` [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line Alastair D'Silva
2019-04-12 13:48 ` Petr Mladek
2019-04-12 23:22 ` Alastair D'Silva
2019-04-15 9:02 ` Petr Mladek
2019-04-15 10:29 ` Alastair D'Silva
2019-04-15 10:56 ` David Laight
2019-04-15 10:59 ` Alastair D'Silva
[not found] ` <20190410031720.11067-1-alastair-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org>
2019-04-10 3:17 ` [PATCH 2/4] lib/hexdump.c: Optionally suppress lines of filler bytes Alastair D'Silva
2019-04-10 3:32 ` Alastair D'Silva
2019-04-12 14:03 ` Petr Mladek
2019-04-12 23:28 ` Alastair D'Silva
2019-04-15 9:18 ` Petr Mladek
2019-04-15 10:33 ` Alastair D'Silva
2019-04-10 3:17 ` [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags Alastair D'Silva
2019-04-10 6:56 ` Dan Carpenter
2019-04-12 14:12 ` Petr Mladek
2019-04-12 23:31 ` Alastair D'Silva
2019-04-15 9:24 ` Petr Mladek
2019-04-15 10:07 ` Alastair D'Silva
2019-04-15 10:20 ` David Laight
2019-04-15 10:44 ` Alastair D'Silva
2019-04-15 11:03 ` David Laight
2019-04-15 11:12 ` Alastair D'Silva
2019-04-12 14:47 ` Tvrtko Ursulin
2019-04-10 3:17 ` [PATCH 4/4] lib/hexdump.c: Allow multiple groups to be separated by lines '|' Alastair D'Silva
2019-04-10 8:45 ` David Laight
2019-04-10 9:52 ` Alastair D'Silva
2019-04-10 8:53 ` Sergey Senozhatsky
2019-04-10 17:53 ` Patchwork [this message]
2019-04-10 18:17 ` ✓ Fi.CI.BAT: success for Hexdump enhancements Patchwork
2019-04-11 3:22 ` ✓ Fi.CI.IGT: " Patchwork
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=20190410175320.19551.64933@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=alastair@au1.ibm.com \
--cc=intel-gfx@lists.freedesktop.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