linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Matthew Auld <matthew.auld@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] 5.9-rc1: graphics regression moved from -next to mainline
Date: Tue, 25 Aug 2020 12:55:25 +0300	[thread overview]
Message-ID: <87tuwr59te.fsf@intel.com> (raw)
In-Reply-To: <20200821091900.hzbivycs5ky5d3iw@duo.ucw.cz>

On Fri, 21 Aug 2020, Pavel Machek <pavel@ucw.cz> wrote:
> On Thu 2020-08-20 09:16:18, Linus Torvalds wrote:
>> On Thu, Aug 20, 2020 at 2:23 AM Pavel Machek <pavel@ucw.cz> wrote:
>> >
>> > Yes, it seems they make things work. (Chris asked for new patch to be
>> > tested, so I am switching to his kernel, but it survived longer than
>> > it usually does.)
>> 
>> Ok, so at worst we know how to solve it, at best the reverts won't be
>> needed because Chris' patch will fix the issue properly.
>> 
>> So I'll archive this thread, but remind me if this hasn't gotten
>> sorted out in the later rc's.
>
> Yes, thank you, it seems we have a solution w/o the revert.

For posterity, I'm told the fix is [1].

BR,
Jani.


[1] https://lore.kernel.org/intel-gfx/20200821123746.16904-1-joro@8bytes.org/


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2020-08-25  9:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 16:11 5.9-rc1: graphics regression moved from -next to mainline Pavel Machek
2020-08-19  0:38 ` Linus Torvalds
2020-08-19  1:12   ` [Intel-gfx] " Dave Airlie
2020-08-19  1:59     ` Linus Torvalds
2020-08-19 16:57       ` Pavel Machek
2020-08-19 20:19       ` Pavel Machek
2020-08-20  9:23       ` Pavel Machek
2020-08-20 16:16         ` Linus Torvalds
2020-08-21  9:19           ` Pavel Machek
2020-08-25  9:55             ` Jani Nikula [this message]
2020-08-25 16:31               ` Harald Arnesen
2020-08-25 18:19                 ` Linus Torvalds
2020-08-25 21:38                   ` Harald Arnesen
2020-08-26  8:36                   ` Harald Arnesen
2020-08-26  9:30                     ` Harald Arnesen
2020-08-26 18:04                       ` Linus Torvalds
2020-08-26 20:44                         ` Harald Arnesen
2020-08-26 20:47                           ` Dave Airlie
2020-08-26 20:53                             ` Harald Arnesen
2020-08-26 20:59                               ` Linus Torvalds
2020-08-27  7:14                                 ` Harald Arnesen
2020-08-27  7:28                                   ` Pavel Machek
2020-09-01 11:57                                 ` Harald Arnesen
2020-09-09  9:15                                   ` Pavel Machek

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=87tuwr59te.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=pavel@ucw.cz \
    --cc=rodrigo.vivi@intel.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 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).