All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Kees Cook" <keescook@chromium.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp: Actually read Adjust Request Post Cursor2 register
Date: Fri, 03 Dec 2021 11:47:21 -0000	[thread overview]
Message-ID: <163853204128.5406.6633165921222442126@emeril.freedesktop.org> (raw)
In-Reply-To: <20211203092517.3592532-1-keescook@chromium.org>

== Series Details ==

Series: drm/dp: Actually read Adjust Request Post Cursor2 register
URL   : https://patchwork.freedesktop.org/series/97533/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
1de58e82192d drm/dp: Actually read Adjust Request Post Cursor2 register
-:15: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#15: 
  147 | u8 drm_dp_get_adjust_request_post_cursor(const u8 link_status[DP_LINK_STATUS_SIZE],

total: 0 errors, 1 warnings, 0 checks, 37 lines checked



  reply	other threads:[~2021-12-03 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  9:25 [PATCH v2] drm/dp: Actually read Adjust Request Post Cursor2 register Kees Cook
2021-12-03  9:25 ` [Intel-gfx] " Kees Cook
2021-12-03  9:25 ` Kees Cook
2021-12-03 11:47 ` Patchwork [this message]
2021-12-03 11:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2021-12-03 12:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-03 15:28 ` [PATCH v2] " Thierry Reding
2021-12-03 15:28   ` [Intel-gfx] " Thierry Reding
2021-12-03 15:28   ` Thierry Reding
2021-12-04  0:30   ` [Intel-gfx] " Kees Cook
2021-12-04  0:30     ` Kees Cook
2021-12-04  0:30     ` Kees Cook
2021-12-03 16:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " 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=163853204128.5406.6633165921222442126@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keescook@chromium.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 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.