From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: intel-gfx@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
stable@vger.kernel.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [Regression] drm/i915: Don't use BAR mappings for ring buffers with LLC alone creates issues in stable kernels
Date: Mon, 20 Mar 2023 14:28:36 +0100 [thread overview]
Message-ID: <ZBhfhJ0ylxqXPHee@kroah.com> (raw)
In-Reply-To: <a0be2b31-9e72-1254-978e-570b27abb364@manjaro.org>
On Sun, Mar 19, 2023 at 10:01:01AM +0700, Philip Müller wrote:
> Have to correct the affected kernels to these: 4.14.310, 4.19.278, 5.4.237,
> 5.10.175
Please don't top-post :(
Anyway, should be fixed in the next round of releases in a few days, if
not, please let us know.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: John Harrison <John.C.Harrison@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Regression] drm/i915: Don't use BAR mappings for ring buffers with LLC alone creates issues in stable kernels
Date: Mon, 20 Mar 2023 14:28:36 +0100 [thread overview]
Message-ID: <ZBhfhJ0ylxqXPHee@kroah.com> (raw)
In-Reply-To: <a0be2b31-9e72-1254-978e-570b27abb364@manjaro.org>
On Sun, Mar 19, 2023 at 10:01:01AM +0700, Philip Müller wrote:
> Have to correct the affected kernels to these: 4.14.310, 4.19.278, 5.4.237,
> 5.10.175
Please don't top-post :(
Anyway, should be fixed in the next round of releases in a few days, if
not, please let us know.
greg k-h
next prev parent reply other threads:[~2023-03-20 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 2:48 [Regression] drm/i915: Don't use BAR mappings for ring buffers with LLC alone creates issues in stable kernels Philip Müller
2023-03-19 3:01 ` Philip Müller
2023-03-20 13:28 ` Greg Kroah-Hartman [this message]
2023-03-20 13:28 ` Greg Kroah-Hartman
2023-03-21 0:58 ` [Intel-gfx] " Philip Müller
2023-03-21 0:58 ` Philip Müller
2023-03-21 7:12 ` [Intel-gfx] " Greg Kroah-Hartman
2023-03-21 7:12 ` Greg Kroah-Hartman
2023-03-21 12:16 ` [Intel-gfx] " Philip Müller
2023-03-21 12:16 ` Philip Müller
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=ZBhfhJ0ylxqXPHee@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=philm@manjaro.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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.