From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Hampson, Steven T" <steven.t.hampson@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix NULL pointer found by static analysis (rev2)
Date: Wed, 23 Sep 2020 21:57:38 -0000 [thread overview]
Message-ID: <160089825865.4493.15793328197447802001@emeril.freedesktop.org> (raw)
In-Reply-To: <20200923044054.5653-1-steven.t.hampson@intel.com>
== Series Details ==
Series: Fix NULL pointer found by static analysis (rev2)
URL : https://patchwork.freedesktop.org/series/81999/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3a559b7eb929 Fix NULL pointer found by static analysis
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Steve Hampson
-:30: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Intel-gfx <intel-gfx-bounces@lists.freedesktop.org>'
total: 0 errors, 2 warnings, 0 checks, 8 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:[~2020-09-23 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 4:40 [Intel-gfx] [PATCH] Fix NULL pointer found by static analysis Steve Hampson
2020-09-23 5:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-09-23 8:48 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-09-23 8:58 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-09-23 9:04 ` Jani Nikula
2020-09-23 21:23 ` Hampson, Steven T
2020-09-23 21:57 ` Patchwork [this message]
2020-09-23 22:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix NULL pointer found by static analysis (rev2) Patchwork
2020-09-24 1:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=160089825865.4493.15793328197447802001@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=steven.t.hampson@intel.com \
/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).