From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm: Remove defunct dma_buf_kmap stubs
Date: Tue, 07 Aug 2018 17:53:30 -0000 [thread overview]
Message-ID: <20180807175330.1838.1389@emeril.freedesktop.org> (raw)
In-Reply-To: <20180807174748.4503-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm: Remove defunct dma_buf_kmap stubs
URL : https://patchwork.freedesktop.org/series/47829/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ee6d380149a7 drm: Remove defunct dma_buf_kmap stubs
-:13: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#13:
References: 09ea0dfbf972 ("dma-buf: make map_atomic and map function pointers optional")
-:13: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 09ea0dfbf972 ("dma-buf: make map_atomic and map function pointers optional")'
#13:
References: 09ea0dfbf972 ("dma-buf: make map_atomic and map function pointers optional")
total: 1 errors, 1 warnings, 0 checks, 59 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-08-07 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:47 [PATCH] drm: Remove defunct dma_buf_kmap stubs Chris Wilson
2018-08-07 17:53 ` Patchwork [this message]
[not found] ` <20180807174748.4503-1-chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
2018-08-07 17:54 ` Christian König
2018-08-07 17:55 ` Daniel Vetter
2018-08-07 18:09 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-08-07 18:20 ` Chris Wilson
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=20180807175330.1838.1389@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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.