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: manual merge of the drm-misc tree with the drm tree
Date: Tue, 11 Jun 2019 03:59:33 -0000 [thread overview]
Message-ID: <20190611035933.9310.61452@emeril.freedesktop.org> (raw)
In-Reply-To: <20190611135202.145424e5@canb.auug.org.au>
== Series Details ==
Series: linux-next: manual merge of the drm-misc tree with the drm tree
URL : https://patchwork.freedesktop.org/series/61878/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e0a1e1173fb0 linux-next: manual merge of the drm-misc tree with the drm tree
-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 9b93eb475aa9 ("drm/amd/display: move clk_mgr files to right place")'
#15:
9b93eb475aa9 ("drm/amd/display: move clk_mgr files to right place")
-:35: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#35:
Subject: [PATCH] drm/amd/display: merge fix for "drm/amd: drop use of drmp.h in os_types.h"
total: 1 errors, 1 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:[~2019-06-11 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 3:52 linux-next: manual merge of the drm-misc tree with the drm tree Stephen Rothwell
2019-06-11 3:59 ` Patchwork [this message]
2019-06-11 4:25 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-12 9:33 ` ✓ 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=20190611035933.9310.61452@emeril.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox