All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jun Lei <Jun.Lei@amd.com>,
	Mustapha Ghaddar <mustapha.ghaddar@amd.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>,
	Daniel Wheeler <daniel.wheeler@amd.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"Wentland, Harry" <harry.wentland@amd.com>,
	Dave Airlie <airlied@gmail.com>,
	"Koenig, Christian" <christian.koenig@amd.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Tue, 11 Jan 2022 10:08:08 -0500	[thread overview]
Message-ID: <CADnq5_OZR9Ft=WVVbpM_WUpFZurni4yVxGPpa4nDkhupmod_ag@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whSAYiO_TkKut6XckdQigFj39ft1Kcs2qJe5niHWPGdwg@mail.gmail.com>

On Mon, Jan 10, 2022 at 9:53 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Jan 10, 2022 at 6:44 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I'll double-check to see if a revert fixes it at the top of my tree.
>
> Yup. It reverts cleanly, and the end result builds and works fine, and
> doesn't show the horrendous flickering.
>
> I have done that revert, and will continue the merge window work.
> Somebody else gets to figure out what the actual bug is, but that
> commit was horribly broken on my machine (Sapphire Pulse RX 580 8GB,
> fwiw).

Thanks for tracking this down.  We are investigating the issue.

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>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>,
	Daniel Wheeler <daniel.wheeler@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	Jun Lei <Jun.Lei@amd.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	"Koenig, Christian" <christian.koenig@amd.com>,
	Mustapha Ghaddar <mustapha.ghaddar@amd.com>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Tue, 11 Jan 2022 10:08:08 -0500	[thread overview]
Message-ID: <CADnq5_OZR9Ft=WVVbpM_WUpFZurni4yVxGPpa4nDkhupmod_ag@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whSAYiO_TkKut6XckdQigFj39ft1Kcs2qJe5niHWPGdwg@mail.gmail.com>

On Mon, Jan 10, 2022 at 9:53 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Jan 10, 2022 at 6:44 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I'll double-check to see if a revert fixes it at the top of my tree.
>
> Yup. It reverts cleanly, and the end result builds and works fine, and
> doesn't show the horrendous flickering.
>
> I have done that revert, and will continue the merge window work.
> Somebody else gets to figure out what the actual bug is, but that
> commit was horribly broken on my machine (Sapphire Pulse RX 580 8GB,
> fwiw).

Thanks for tracking this down.  We are investigating the issue.

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>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>,
	Daniel Wheeler <daniel.wheeler@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	"Wentland, Harry" <harry.wentland@amd.com>,
	Dave Airlie <airlied@gmail.com>, Jun Lei <Jun.Lei@amd.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	"Koenig, Christian" <christian.koenig@amd.com>,
	Mustapha Ghaddar <mustapha.ghaddar@amd.com>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Tue, 11 Jan 2022 10:08:08 -0500	[thread overview]
Message-ID: <CADnq5_OZR9Ft=WVVbpM_WUpFZurni4yVxGPpa4nDkhupmod_ag@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whSAYiO_TkKut6XckdQigFj39ft1Kcs2qJe5niHWPGdwg@mail.gmail.com>

On Mon, Jan 10, 2022 at 9:53 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Jan 10, 2022 at 6:44 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I'll double-check to see if a revert fixes it at the top of my tree.
>
> Yup. It reverts cleanly, and the end result builds and works fine, and
> doesn't show the horrendous flickering.
>
> I have done that revert, and will continue the merge window work.
> Somebody else gets to figure out what the actual bug is, but that
> commit was horribly broken on my machine (Sapphire Pulse RX 580 8GB,
> fwiw).

Thanks for tracking this down.  We are investigating the issue.

Alex

  reply	other threads:[~2022-01-11 15:08 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  6:12 [git pull] drm for 5.17-rc1 (pre-merge window pull) Dave Airlie
2022-01-07  6:12 ` Dave Airlie
2022-01-07 10:37 ` Christian König
2022-01-07 10:37   ` Christian König
2022-01-10 21:10 ` Linus Torvalds
2022-01-10 21:27 ` pr-tracker-bot
2022-01-10 21:27   ` pr-tracker-bot
2022-01-10 21:30 ` Linus Torvalds
2022-01-10 22:04   ` Daniel Vetter
2022-01-10 22:04     ` Daniel Vetter
2022-01-10 22:04     ` Daniel Vetter
2022-01-10 22:13     ` Alex Deucher
2022-01-10 22:13       ` Alex Deucher
2022-01-10 22:13       ` Alex Deucher
2022-01-11  1:04       ` Linus Torvalds
2022-01-11  1:04         ` Linus Torvalds
2022-01-11  1:04         ` Linus Torvalds
2022-01-11  1:11         ` Alex Deucher
2022-01-11  1:11           ` Alex Deucher
2022-01-11  1:11           ` Alex Deucher
2022-01-11  1:21           ` Linus Torvalds
2022-01-11  1:21             ` Linus Torvalds
2022-01-11  1:21             ` Linus Torvalds
2022-01-11  1:28             ` Linus Torvalds
2022-01-11  1:28               ` Linus Torvalds
2022-01-11  1:28               ` Linus Torvalds
2022-01-11  2:22             ` Linus Torvalds
2022-01-11  2:22               ` Linus Torvalds
2022-01-11  2:22               ` Linus Torvalds
2022-01-11  2:44               ` Linus Torvalds
2022-01-11  2:44                 ` Linus Torvalds
2022-01-11  2:44                 ` Linus Torvalds
2022-01-11  2:52                 ` Linus Torvalds
2022-01-11  2:52                   ` Linus Torvalds
2022-01-11  2:52                   ` Linus Torvalds
2022-01-11 15:08                   ` Alex Deucher [this message]
2022-01-11 15:08                     ` Alex Deucher
2022-01-11 15:08                     ` Alex Deucher
2022-01-11 15:38                     ` Harry Wentland
2022-01-11 15:38                       ` Harry Wentland
2022-01-11 15:38                       ` Harry Wentland
2022-01-11 20:51                       ` Linus Torvalds
2022-01-11 20:51                         ` Linus Torvalds
2022-01-11 20:51                         ` Linus Torvalds
2022-01-12 15:36                         ` Harry Wentland
2022-01-12 15:36                           ` Harry Wentland
2022-01-12 15:36                           ` Harry Wentland

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_OZR9Ft=WVVbpM_WUpFZurni4yVxGPpa4nDkhupmod_ag@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Jun.Lei@amd.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.wheeler@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meenakshikumar.somasundaram@amd.com \
    --cc=mustapha.ghaddar@amd.com \
    --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.