From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Wayne Lin" <wayne.lin@amd.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2
Date: Thu, 07 Mar 2024 07:20:20 -0000 [thread overview]
Message-ID: <170979602040.580595.2365620815888707390@8e613ede5ea5> (raw)
In-Reply-To: <20240307062957.2323620-1-Wayne.Lin@amd.com>
== Series Details ==
Series: drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2
URL : https://patchwork.freedesktop.org/series/130851/
State : warning
== Summary ==
Error: dim checkpatch failed
54fc3a878567 drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2
-:12: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#12:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload allocation/removement")
-:22: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be immediately followed by Closes: with a URL to the report
#22:
Reported-by: Leon Weiß <leon.weiss@ruhr-uni-bochum.de>
Link: https://lore.kernel.org/r/38c253ea42072cc825dc969ac4e6b9b600371cc8.camel@ruhr-uni-bochum.de/
total: 0 errors, 2 warnings, 0 checks, 53 lines checked
next prev parent reply other threads:[~2024-03-07 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:29 [PATCH] drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2 Wayne Lin
2024-03-07 7:20 ` Patchwork [this message]
2024-03-07 7:20 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-03-07 7:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-07 17:37 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-15 2:55 ` [PATCH] " Lin, Wayne
2024-04-15 20:31 ` ✗ Fi.CI.BUILD: failure for drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2 (rev2) Patchwork
2024-04-18 19:43 ` [PATCH] drm/mst: Fix NULL pointer dereference at drm_dp_add_payload_part2 Harry Wentland
2024-05-09 12:43 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-09 19:18 ` Mario Limonciello
2024-05-10 3:18 ` Lin, Wayne
2024-05-10 9:24 ` Jani Nikula
2024-05-12 16:11 ` Limonciello, Mario
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=170979602040.580595.2365620815888707390@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=wayne.lin@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.