From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Christian König" <christian.koenig@amd.com>,
"Dave Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.11-rc1
Date: Mon, 14 Dec 2020 17:55:49 -0500 [thread overview]
Message-ID: <CADnq5_OV4UqGLTsPnWij=eQYYxGf57mY8Nr34s5Y=jQiG9ZYLw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgLKJ6S0V0YgVWdcXVH9Zh8CEV5xPBUSFkJ7fywNLtqeg@mail.gmail.com>
On Mon, Dec 14, 2020 at 5:45 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Dec 14, 2020 at 2:29 PM Alex Deucher <alexdeucher@gmail.com> wrote:
> >
> > The relevant fixes are:
>
> Ok, I can confirm that applying those two patches gets my workstation
> working properly again.
>
> Would it be possible to get those submitted properly (or I can just
> take them as-is, but would like to get a "please just pick them
> directly")?
>
> I don't like to continue to do merges during the merge windows with a
> known broken base - it makes for a nightmare of bisection when you
> have multiple independent problems, and I assume this hits not just me
> but a lot of people with radeon/amdgpu graphics?
Yes, anyone using AMD GPUs will be affected. The patches are already
in drm-misc, so they should show up in the next drm -fixes PR, but I
think it would be fine to pick them directly to fix support for
everyone using your tree.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Christian König" <christian.koenig@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.11-rc1
Date: Mon, 14 Dec 2020 17:55:49 -0500 [thread overview]
Message-ID: <CADnq5_OV4UqGLTsPnWij=eQYYxGf57mY8Nr34s5Y=jQiG9ZYLw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgLKJ6S0V0YgVWdcXVH9Zh8CEV5xPBUSFkJ7fywNLtqeg@mail.gmail.com>
On Mon, Dec 14, 2020 at 5:45 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Dec 14, 2020 at 2:29 PM Alex Deucher <alexdeucher@gmail.com> wrote:
> >
> > The relevant fixes are:
>
> Ok, I can confirm that applying those two patches gets my workstation
> working properly again.
>
> Would it be possible to get those submitted properly (or I can just
> take them as-is, but would like to get a "please just pick them
> directly")?
>
> I don't like to continue to do merges during the merge windows with a
> known broken base - it makes for a nightmare of bisection when you
> have multiple independent problems, and I assume this hits not just me
> but a lot of people with radeon/amdgpu graphics?
Yes, anyone using AMD GPUs will be affected. The patches are already
in drm-misc, so they should show up in the next drm -fixes PR, but I
think it would be fine to pick them directly to fix support for
everyone using your tree.
Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-12-14 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 3:52 [git pull] drm for 5.11-rc1 Dave Airlie
2020-12-11 3:52 ` Dave Airlie
2020-12-14 19:51 ` pr-tracker-bot
2020-12-14 19:51 ` pr-tracker-bot
2020-12-14 22:21 ` Linus Torvalds
2020-12-14 22:21 ` Linus Torvalds
2020-12-14 22:28 ` Alex Deucher
2020-12-14 22:28 ` Alex Deucher
2020-12-14 22:45 ` Linus Torvalds
2020-12-14 22:45 ` Linus Torvalds
2020-12-14 22:55 ` Alex Deucher [this message]
2020-12-14 22:55 ` Alex Deucher
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='CADnq5_OV4UqGLTsPnWij=eQYYxGf57mY8Nr34s5Y=jQiG9ZYLw@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.