From: Patchwork <patchwork@emeril.freedesktop.org>
To: Steven Price <Steven.Price@arm.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] dma_resv: prime lockdep annotations (rev2)
Date: Mon, 11 Nov 2019 18:12:50 -0000 [thread overview]
Message-ID: <157349597017.29961.11683206982962746300@emeril.freedesktop.org> (raw)
In-Reply-To: <20191104173801.2972-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/3] dma_resv: prime lockdep annotations (rev2)
URL : https://patchwork.freedesktop.org/series/68958/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
87afb1ee808f dma_resv: prime lockdep annotations
-:106: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#106:
> @@ -95,6 +96,29 @@ static void dma_resv_list_free(struct dma_resv_list *list)
-:148: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("f42d23dbcca2da2f8")'
#148:
From d07ea81611ed6e4fb8cc290f42d23dbcca2da2f8 Mon Sep 17 00:00:00 2001
total: 1 errors, 1 warnings, 0 checks, 23 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Steven Price" <Steven.Price@arm.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] dma_resv: prime lockdep annotations (rev2)
Date: Mon, 11 Nov 2019 18:12:50 -0000 [thread overview]
Message-ID: <157349597017.29961.11683206982962746300@emeril.freedesktop.org> (raw)
Message-ID: <20191111181250.gliPQxEMEHr8S5OpsMKuAdh4yBkfOOlJT_IsrWWtZQY@z> (raw)
In-Reply-To: <20191104173801.2972-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/3] dma_resv: prime lockdep annotations (rev2)
URL : https://patchwork.freedesktop.org/series/68958/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
87afb1ee808f dma_resv: prime lockdep annotations
-:106: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#106:
> @@ -95,6 +96,29 @@ static void dma_resv_list_free(struct dma_resv_list *list)
-:148: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("f42d23dbcca2da2f8")'
#148:
From d07ea81611ed6e4fb8cc290f42d23dbcca2da2f8 Mon Sep 17 00:00:00 2001
total: 1 errors, 1 warnings, 0 checks, 23 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-11-11 18:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:37 [PATCH 1/3] dma_resv: prime lockdep annotations Daniel Vetter
2019-11-04 17:37 ` [Intel-gfx] " Daniel Vetter
2019-11-04 17:37 ` Daniel Vetter
[not found] ` <20191104173801.2972-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2019-11-04 17:38 ` [PATCH 2/3] drm/nouveau: slowpath for pushbuf ioctl Daniel Vetter
2019-11-04 17:38 ` [Intel-gfx] " Daniel Vetter
2019-11-04 17:38 ` Daniel Vetter
2019-11-05 11:04 ` Daniel Vetter
2019-11-05 11:04 ` [Intel-gfx] " Daniel Vetter
2019-11-05 11:04 ` Daniel Vetter
[not found] ` <20191105110419.GG10326-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-11-05 12:30 ` Maarten Lankhorst
2019-11-05 12:30 ` [Intel-gfx] " Maarten Lankhorst
2019-11-05 12:30 ` Maarten Lankhorst
2019-11-04 17:38 ` [PATCH 3/3] drm/ttm: remove ttm_bo_wait_unreserved Daniel Vetter
2019-11-04 17:38 ` [Intel-gfx] " Daniel Vetter
2019-11-06 10:24 ` Daniel Vetter
2019-11-06 10:24 ` [Intel-gfx] " Daniel Vetter
2019-11-04 17:48 ` [PATCH 1/3] dma_resv: prime lockdep annotations Daniel Vetter
2019-11-04 17:48 ` [Intel-gfx] " Daniel Vetter
2019-11-04 17:48 ` Daniel Vetter
2019-11-04 20:01 ` Koenig, Christian
2019-11-04 20:01 ` [Intel-gfx] " Koenig, Christian
2019-11-04 20:01 ` Koenig, Christian
2019-11-04 20:55 ` Daniel Vetter
2019-11-04 20:55 ` [Intel-gfx] " Daniel Vetter
2019-11-04 20:55 ` Daniel Vetter
2019-11-04 21:00 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] " Patchwork
2019-11-04 21:00 ` [Intel-gfx] " Patchwork
2019-11-04 21:22 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-04 21:22 ` [Intel-gfx] " Patchwork
2019-11-05 8:31 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-05 8:31 ` [Intel-gfx] " Patchwork
2019-11-11 13:11 ` [PATCH 1/3] " Steven Price
2019-11-11 13:11 ` [Intel-gfx] " Steven Price
2019-11-11 15:42 ` Daniel Vetter
2019-11-11 15:42 ` [Intel-gfx] " Daniel Vetter
2019-11-11 15:42 ` Daniel Vetter
2019-11-14 11:50 ` Steven Price
2019-11-14 11:50 ` [Intel-gfx] " Steven Price
2019-11-14 11:50 ` Steven Price
2019-11-20 10:51 ` Daniel Vetter
2019-11-20 10:51 ` [Intel-gfx] " Daniel Vetter
2019-11-11 18:12 ` Patchwork [this message]
2019-11-11 18:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] dma_resv: prime lockdep annotations (rev2) Patchwork
2019-11-11 18:48 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-11-11 18:48 ` [Intel-gfx] " 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=157349597017.29961.11683206982962746300@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=Steven.Price@arm.com \
--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.