From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Leo Li <sunpeng.li@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Kent Russell <kent.russell@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
Ken Chalmers <ken.chalmers@amd.com>
Subject: linux-next: Fixes tags need some work in the drm tree
Date: Fri, 1 Feb 2019 10:57:36 +1100 [thread overview]
Message-ID: <20190201105736.1428c9fc@canb.auug.org.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1380 bytes --]
Hi all,
In commit
a93587b31e34 ("drm/amd/display: Only get the connector state for VRR when toggled")
Fixes tag
Fixes: 3cc22f281318 ("drm/amdgpu: Set FreeSync state using drm VRR properties")
has these problem(s):
- Target SHA1 does not exist
Maybe instead:
FIxes: bb47de736661 ("drm/amdgpu: Set FreeSync state using drm VRR properties")
In commit
32e61361b82e ("drm/amd/display: Fix 64-bit division for 32-bit builds")
Fixes tag
Fixes: https://lists.freedesktop.org/archives/dri-devel/2018-December/201008.html
has these problem(s):
- No SHA1 recognised
Maybe instead:
Fixes: 80604e27bc9 ("drm/amd/display: Use 100 Hz precision for pipe pixel clocks")
In commit
c4312c27c826 ("drm/amdgpu: Cleanup 2 compiler warnings")
Fixes tag
Fixes: e4ae0fc drm/amdgpu: implement gfx8 post_soft_reset
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
Fixes tag
Fixes: 5e01c09 drm/amdgpu/gfx_v8_0: Reorder the gfx, kiq and kcq rings
has these problem(s):
- Target SHA1 does not exist
Maybe instead:
Fixes: c6064de4b734 ("drm/amdgpu/gfx_v8_0: Reorder the gfx, kiq and kcq rings test sequence")
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-31 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 23:57 Stephen Rothwell [this message]
2019-02-01 10:05 ` linux-next: Fixes tags need some work in the drm tree Daniel Vetter
2019-02-01 10:48 ` Stephen Rothwell
2019-02-01 20:34 ` Alex Deucher
2019-02-04 9:13 ` Daniel Vetter
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=20190201105736.1428c9fc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ken.chalmers@amd.com \
--cc=kent.russell@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicholas.kazlauskas@amd.com \
--cc=sunpeng.li@amd.com \
/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