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-intel tree
Date: Tue, 08 May 2018 01:19:07 -0000 [thread overview]
Message-ID: <20180508011907.28243.57504@emeril.freedesktop.org> (raw)
In-Reply-To: <20180508110716.53dfef41@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the drm-intel tree
URL : https://patchwork.freedesktop.org/series/42839/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3c1454cc91d5 linux-next: build failure after merge of the drm-intel tree
-:25: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend")'
#25:
c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend")
-:37: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#37:
Subject: [PATCH] drm/xen-front: merge fix for "drivers: remove force dma flag from buses"
total: 1 errors, 1 warnings, 0 checks, 10 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:[~2018-05-08 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 1:07 linux-next: build failure after merge of the drm-intel tree Stephen Rothwell
2018-05-08 1:19 ` Patchwork [this message]
2018-05-08 1:36 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-05-08 1:40 ` Stephen Rothwell
2018-05-08 6:11 ` Saarinen, Jani
2018-05-08 12:28 ` Arkadiusz Hiler
2018-05-08 7:08 ` Oleksandr Andrushchenko
2018-05-09 5:02 ` Stephen Rothwell
2018-05-09 5:08 ` Christoph Hellwig
2018-05-09 5:18 ` Stephen Rothwell
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=20180508011907.28243.57504@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;
as well as URLs for NNTP newsgroup(s).