From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: linux-next: Signed-off-by missing for commits in the drm tree
Date: Wed, 2 Aug 2017 16:54:56 +1000 [thread overview]
Message-ID: <20170802165456.1a2f6eb7@canb.auug.org.au> (raw)
Hi Dave,
Commits
663ebbf63180 "drm/amdgpu: trace VM flags as 64bits"
5327dd8acf05 "drm/amdgpu: remove stale TODO comment"
eabd76cef900 "drm/amd/sched: print sched job id in amd_sched_job trace"
a69c7e0138fc "drm/amdgpu: update pctl1 ram index/data for mmhub on raven"
7504938f8e73 "drm/amdgpu: add check when no firmware need to load"
98a7f88ce9a9 "drm/amdgpu: bind BOs with GTT space allocated directly v2"
92c60d9cf663 "drm/amdgpu: bind BOs to TTM only once"
fc9c8f5459f2 "drm/amdgpu: add vm_needs_flush parameter to amdgpu_copy_buffer"
df264f9e0808 "drm/amdgpu: allow flushing VMID0 before IB execution as well"
369421cbfabf "drm/amdgpu: fix amdgpu_ring_write_multiple"
e8110b1c9bdd "drm/amdgpu: move ring helpers to amdgpu_ring.h"
are missing Signed-off-by from their comitter.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-08-02 6:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 6:54 Stephen Rothwell [this message]
2017-08-29 1:44 linux-next: Signed-off-by missing for commits in the drm tree Stephen Rothwell
2017-08-29 1:51 ` Sinclair Yeh
2017-12-03 23:57 Stephen Rothwell
2017-12-04 2:32 ` Zhenyu Wang
2017-12-05 2:45 Stephen Rothwell
2017-12-05 9:36 ` Laurent Pinchart
2017-12-21 5:12 Stephen Rothwell
2017-12-21 11:40 ` Tomi Valkeinen
2017-12-21 13:06 ` Daniel Vetter
2018-03-21 9:27 Stephen Rothwell
2018-03-23 11:55 ` Tomi Valkeinen
2018-05-15 23:18 Stephen Rothwell
2018-05-17 15:27 ` Koo, Anthony
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=20170802165456.1a2f6eb7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).