From: David Laight <David.Laight@ACULAB.COM>
To: 'Thomas Zimmermann' <tzimmermann@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Huang, Ray" <ray.huang@amd.com>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>
Subject: RE: Linux 5.10-rc4; graphics alignment
Date: Fri, 20 Nov 2020 11:45:22 +0000 [thread overview]
Message-ID: <fa6346190d0b4936934d1f1359e5b71f@AcuMS.aculab.com> (raw)
In-Reply-To: <c9bae016-413f-0db9-c9ee-d6f39d24a6ab@suse.de>
From: Thomas Zimmermann
> Sent: 20 November 2020 11:27
...
> >> You can use drm-tip for testing, where many of the DRM patches go through.
> >>
> >> https://cgit.freedesktop.org/drm/drm-tip/
> >>
> >> It's fairly up-to-date.
> >
> > Any idea of tags either side of the 5.10 merge?
>
> The final commit before v5.9 appears to be
>
> Fixes: 33c8256b3bcc ("drm/amd/display: Change ABM config init interface")
>
> I'd try this as a good commit. For the bad commit, just try HEAD.
HEAD off that tree works.
Colours ok and no stack backtrace.
Ideas??
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-11-20 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 9:52 Linux 5.10-rc4; graphics alignment David Laight
2020-11-20 10:13 ` Thomas Zimmermann
2020-11-20 10:51 ` David Laight
2020-11-20 11:26 ` Thomas Zimmermann
2020-11-20 11:45 ` David Laight [this message]
2020-11-20 12:30 ` Thomas Zimmermann
2020-11-20 12:53 ` David Laight
2020-11-20 13:41 ` Thomas Zimmermann
2020-11-20 15:39 ` David Laight
2020-11-24 16:27 ` David Laight
2020-11-25 7:53 ` Thomas Zimmermann
2020-11-25 8:25 ` Thomas Zimmermann
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=fa6346190d0b4936934d1f1359e5b71f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/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).