From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: linux@treblig.org, alexander.deucher@amd.com,
christian.koenig@amd.com, harry.wentland@amd.com,
sunpeng.li@amd.com, amd-gfx@lists.freedesktop.org,
airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] drm/amdgpu: Remove is_idle method
Date: Wed, 26 Aug 2026 15:09:33 +0200 [thread overview]
Message-ID: <2026082654-gangrene-support-8541@gregkh> (raw)
In-Reply-To: <CADnq5_N0AxaDZswgEQ7BEcKw8mF2hnSbAQp-w9U2Fy-MaEw8Rg@mail.gmail.com>
On Wed, Aug 26, 2026 at 08:45:29AM -0400, Alex Deucher wrote:
> On Wed, Aug 26, 2026 at 6:21 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Aug 17, 2026 at 11:27:41AM -0400, Alex Deucher wrote:
> > > Applied. Thanks.
> >
> > Any hints on where this was applied and if it will get to Linus "soon"?
>
> It will show up in drm-next after the merge window closes. 7.4 material.
Sorry, but this is hitting me now, pre 7.3-rc1. Booting and getting a
zillion kernel warnings isn't ok, that's a regression. Please get this
merged sooner than that.
greg k-h
next prev parent reply other threads:[~2026-08-26 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 18:00 linux
2026-08-15 18:00 ` [PATCH 1/4] drm/amdgpu: Remove is_idle test case linux
2026-08-15 18:00 ` [PATCH 2/4] drm/amdgpu: Remove is_idle (trivial cases) linux
2026-08-15 18:00 ` [PATCH 3/4] drm/amdgpu: Remove is_idle (non trivial functions) linux
2026-08-15 18:00 ` [PATCH 4/4] drm/amdgpu: Remove is_idle linux
2026-08-17 15:27 ` [PATCH 0/4] drm/amdgpu: Remove is_idle method Alex Deucher
2026-08-26 9:24 ` Greg KH
2026-08-26 12:45 ` Alex Deucher
2026-08-26 13:09 ` Greg KH [this message]
2026-08-26 13:10 ` Dr. David Alan Gilbert
2026-08-26 13:24 ` Greg KH
2026-08-26 13:15 ` Alex Deucher
2026-08-26 13:24 ` 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=2026082654-gangrene-support-8541@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=simona@ffwll.ch \
--cc=sunpeng.li@amd.com \
/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
all inboxes | Powered by JetHome®