From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/amdgpu/dc: Stop dma_resv_lock inversion in commit_tail
Date: Mon, 27 Jul 2020 21:40:05 -0000 [thread overview]
Message-ID: <159588600522.26749.3368727665491319037@emeril.freedesktop.org> (raw)
In-Reply-To: <20200727213017.852589-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: drm/amdgpu/dc: Stop dma_resv_lock inversion in commit_tail
URL : https://patchwork.freedesktop.org/series/79937/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
be92e429f9aa drm/amdgpu/dc: Stop dma_resv_lock inversion in commit_tail
-:60: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Daniel Vetter <daniel.vetter@ffwll.ch>'
total: 0 errors, 1 warnings, 0 checks, 26 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:[~2020-07-27 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 21:30 [PATCH] drm/amdgpu/dc: Stop dma_resv_lock inversion in commit_tail Daniel Vetter
2020-07-27 21:30 ` Daniel Vetter
2020-07-27 21:30 ` [Intel-gfx] " Daniel Vetter
2020-07-27 21:30 ` Daniel Vetter
2020-07-27 21:40 ` Patchwork [this message]
2020-07-27 21:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2020-07-27 22:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-27 23:24 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-07-28 6:56 ` [PATCH] " Christian König
2020-07-28 6:56 ` Christian König
2020-07-28 6:56 ` [Intel-gfx] " Christian König
2020-07-28 6:56 ` Christian König
2020-07-29 22:10 ` Alex Deucher
2020-07-29 22:10 ` Alex Deucher
2020-07-29 22:10 ` [Intel-gfx] " Alex Deucher
2020-07-29 22:10 ` Alex Deucher
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=159588600522.26749.3368727665491319037@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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.