From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-intel tree with the drm tree
Date: Wed, 17 Mar 2021 03:34:57 -0000 [thread overview]
Message-ID: <161595209795.17368.12540266890550268036@emeril.freedesktop.org> (raw)
In-Reply-To: <20210317140824.0a28ffec@canb.auug.org.au>
== Series Details ==
Series: linux-next: manual merge of the drm-intel tree with the drm tree
URL : https://patchwork.freedesktop.org/series/88033/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6193c9b6da03 linux-next: manual merge of the drm-intel 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 92f1d09ca4ed ("drm: Switch to %p4cc format modifier")'
#15:
92f1d09ca4ed ("drm: Switch to %p4cc format modifier")
-:19: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 46d12f911821 ("drm/i915: migrate skl planes code new file (v5)")'
#19:
46d12f911821 ("drm/i915: migrate skl planes code new file (v5)")
total: 2 errors, 0 warnings, 0 checks, 18 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:[~2021-03-17 3:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 3:08 linux-next: manual merge of the drm-intel tree with the drm tree Stephen Rothwell
2021-03-17 3:08 ` [Intel-gfx] " Stephen Rothwell
2021-03-17 3:08 ` Stephen Rothwell
2021-03-17 3:34 ` Patchwork [this message]
2021-03-17 4:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-03-17 5:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-03-18 1:52 ` Stephen Rothwell
2021-03-18 1:52 ` [Intel-gfx] " Stephen Rothwell
2021-03-18 1:52 ` Stephen Rothwell
2021-04-29 22:23 ` Stephen Rothwell
2021-04-29 22:23 ` [Intel-gfx] " Stephen Rothwell
2021-04-29 22:23 ` Stephen Rothwell
2021-05-14 1:53 ` Stephen Rothwell
2021-05-14 1:53 ` [Intel-gfx] " Stephen Rothwell
2021-05-14 1:53 ` Stephen Rothwell
2021-05-14 12:14 ` Thomas Zimmermann
2021-05-14 12:14 ` [Intel-gfx] " Thomas Zimmermann
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=161595209795.17368.12540266890550268036@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 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.