From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for linux-next: build failure after merge of the drm-misc tree
Date: Tue, 06 Feb 2024 06:10:55 -0000 [thread overview]
Message-ID: <170719985521.1040578.12105347149573031042@5338d5abeb45> (raw)
In-Reply-To: <20240206152850.333f620d@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/129561/
State : warning
== Summary ==
Error: dim checkpatch failed
89f56ec93511 linux-next: build failure after merge of the drm-misc tree
-:12: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#12:
inlined from 'i915_ttm_get_pages' at drivers/gpu/drm/i915/gem/i915_gem_ttm.c:847:2:
-:23: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit a78a8da51b36 ("drm/ttm: replace busy placement with flags v6")'
#23:
a78a8da51b36 ("drm/ttm: replace busy placement with flags v6")
total: 1 errors, 1 warnings, 0 checks, 8 lines checked
next prev parent reply other threads:[~2024-02-06 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 4:28 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2024-02-06 6:10 ` Patchwork [this message]
2024-02-06 6:24 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-02-06 8:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-12 1:25 ` Stephen Rothwell
2024-02-12 13:15 ` Jani Nikula
2024-02-19 21:48 ` Stephen Rothwell
2024-02-25 21:41 ` Stephen Rothwell
2024-02-25 21:47 ` Stephen Rothwell
2024-02-26 12:56 ` Christian König
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=170719985521.1040578.12105347149573031042@5338d5abeb45 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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.