dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bryan Jennings <bryjen423@gmail.com>
Cc: sashal@kernel.org, airlied@linux.ie,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
	stable@vger.kernel.org, Lang.Yu@amd.com,
	christian.koenig@amd.com
Subject: Re: [PATCH AUTOSEL 5.10 13/22] drm/amdgpu: install stub fence into potential unused fence pointers
Date: Tue, 12 Sep 2023 13:31:26 +0200	[thread overview]
Message-ID: <2023091221-reminder-joylessly-8181@gregkh> (raw)
In-Reply-To: <d32d6919-47cf-4ddc-955a-0759088220ae@gmail.com>

On Sun, Sep 10, 2023 at 03:43:01PM -0500, Bryan Jennings wrote:
> This is also causing log spam on 5.15.  It was included in 5.15.128 as
> commit 4921792e04f2125b5eadef9dbe9417a8354c7eff.  I encountered this and
> found https://gitlab.freedesktop.org/drm/amd/-/issues/2820 while researching
> the problem.

Now reverted, thanks.

greg k-h

  reply	other threads:[~2023-09-12 11:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  1:23 [PATCH AUTOSEL 5.10 01/22] drm/radeon: Fix integer overflow in radeon_cs_parser_init Sasha Levin
2023-07-24  1:24 ` [PATCH AUTOSEL 5.10 13/22] drm/amdgpu: install stub fence into potential unused fence pointers Sasha Levin
2023-08-30 18:53   ` Chia-I Wu
2023-08-31 10:27     ` Christian König
2023-08-31 10:56       ` Greg KH
2023-08-31 13:26         ` Christian König
2023-08-31 14:01           ` Greg KH
2023-08-31 18:55             ` Chia-I Wu
2023-09-01  6:02               ` Christian König
2023-09-04  0:41                 ` Eddie Chapman
2023-08-31 10:29     ` Greg KH
2023-09-10 20:43       ` Bryan Jennings
2023-09-12 11:31         ` Greg KH [this message]
2023-10-07  9:50         ` Greg KH
2023-10-09 12:46           ` Christian König
2023-10-09 18:09             ` Greg KH

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=2023091221-reminder-joylessly-8181@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Lang.Yu@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bryjen423@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --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 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).