From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: linux-next: Fixes tag needs some work in the drm-fixes tree
Date: Fri, 18 Jan 2019 15:42:59 +1100 [thread overview]
Message-ID: <20190118154259.16a7761c@canb.auug.org.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 302 bytes --]
Hi all,
In commit
dddce8b49005 ("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
--
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-18 4:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 4:42 Stephen Rothwell [this message]
2019-02-08 11:01 linux-next: Fixes tag needs some work in the drm-fixes tree Stephen Rothwell
2019-02-08 11:31 ` Heiko Stübner
2019-02-08 11:40 ` Stephen Rothwell
2019-02-08 11:45 ` Heiko Stübner
2019-04-17 21:46 Stephen Rothwell
2019-04-18 7:39 ` Daniel Vetter
2019-05-31 6:11 Stephen Rothwell
2019-12-12 11:52 Stephen Rothwell
2019-12-12 12:35 ` Hans de Goede
2020-07-27 13:38 Stephen Rothwell
2020-07-28 9:50 ` Daniel Vetter
2020-10-30 4:42 Stephen Rothwell
2021-10-12 10:36 Stephen Rothwell
2022-10-28 4:35 Stephen Rothwell
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=20190118154259.16a7761c@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=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;
as well as URLs for NNTP newsgroup(s).