From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for dma-buf: add struct dma_buf_attach_info v2
Date: Tue, 30 Apr 2019 13:49:52 -0000 [thread overview]
Message-ID: <20190430134952.26875.16930@emeril.freedesktop.org> (raw)
In-Reply-To: <20190430111002.106168-1-christian.koenig@amd.com>
== Series Details ==
Series: dma-buf: add struct dma_buf_attach_info v2
URL : https://patchwork.freedesktop.org/series/60107/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e090409de568 dma-buf: add struct dma_buf_attach_info v2
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
Add a structure for the parameters of dma_buf_attach, this makes it much easier
-:353: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Christian König <ckoenig.leichtzumerken@gmail.com>'
total: 0 errors, 2 warnings, 0 checks, 260 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-04-30 13:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 11:10 [PATCH] dma-buf: add struct dma_buf_attach_info v2 Christian König
2019-04-30 11:10 ` [Xen-devel] " Christian König
2019-04-30 13:49 ` Patchwork [this message]
2019-04-30 14:05 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-04-30 15:23 ` [PATCH] " kbuild test robot
2019-04-30 15:23 ` [Xen-devel] [Intel-gfx] " kbuild test robot
2019-04-30 15:23 ` kbuild test robot
2019-04-30 15:23 ` kbuild test robot
2019-04-30 16:59 ` Boris Ostrovsky
2019-04-30 16:59 ` Boris Ostrovsky
2019-04-30 16:59 ` [Xen-devel] " Boris Ostrovsky
2019-04-30 16:59 ` Boris Ostrovsky
2019-04-30 17:31 ` Russell King - ARM Linux admin
2019-04-30 17:31 ` [Xen-devel] " Russell King - ARM Linux admin
2019-05-03 12:05 ` Christian König
2019-05-03 12:05 ` Christian König
2019-05-03 12:05 ` [Xen-devel] " Christian König
2019-05-03 12:09 ` [Intel-gfx] " Daniel Vetter
2019-05-03 12:09 ` [Xen-devel] " Daniel Vetter
2019-05-03 12:09 ` Daniel Vetter
2019-05-03 12:15 ` Koenig, Christian
2019-05-03 12:15 ` [Xen-devel] " Koenig, Christian
2019-05-03 12:15 ` Koenig, Christian
2019-05-03 12:15 ` Koenig, Christian
2019-05-03 12:09 ` Daniel Vetter
2019-04-30 17:31 ` Russell King - ARM Linux admin
2019-04-30 23:06 ` [Intel-gfx] " kbuild test robot
2019-04-30 23:06 ` kbuild test robot
2019-04-30 23:06 ` [Xen-devel] [Intel-gfx] " kbuild test robot
2019-05-01 4:44 ` ✗ Fi.CI.IGT: failure for " Patchwork
2019-05-02 7:59 ` Patchwork
2019-05-02 8:54 ` 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=20190430134952.26875.16930@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.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.