dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Missing AMDGPU drm-fixes-6.4 merges
Date: Wed, 05 Jul 2023 14:35:22 +0200	[thread overview]
Message-ID: <87v8eylenp.wl-tiwai@suse.de> (raw)
In-Reply-To: <CADnq5_Ps7NJ8NiK8s=aTtVjXjttOZtDVH96ToFu6co4DKRFPMg@mail.gmail.com>

On Wed, 05 Jul 2023 14:17:20 +0200,
Alex Deucher wrote:
> 
> On Wed, Jul 5, 2023 at 2:26 AM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > Hi Dave, Alex,
> >
> > it seems that the last PR for AMDGPU 6.4 fixes wasn't taken by Linus
> > due to the missing signed tag:
> >   https://lore.kernel.org/lkml/CAHk-=wiOCgiwzVPOwORHPML9eBphnbtM2DhRcv+v=-tnRrgbYg@mail.gmail.com/
> >
> > And more importantly, this series isn't seen on linux-next, either; so
> > the whole fixes are missing in the upstream.  Could you check it?
> 
> I included all of the necessary changes in last week's 6.5 fixes PR.
> Once that lands, I'll make sure the necessary changes make it to
> stable.

Great, thanks for the update!

Another bug report (for Leap 15.5) showed that the series fixed some
nasty suspend/resume issue, so let's hope that all those get merged
soon :)


Takashi

> 
> Alex
> 
> >
> > FWIW, I stumbled on this due to a recent regression report on openSUSE
> > Tumbleweed:
> >   https://bugzilla.suse.com/show_bug.cgi?id=1212848
> >
> >
> > thanks,
> >
> > Takashi
> 

      reply	other threads:[~2023-07-05 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  6:26 Missing AMDGPU drm-fixes-6.4 merges Takashi Iwai
2023-07-05 12:17 ` Alex Deucher
2023-07-05 12:35   ` Takashi Iwai [this message]

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=87v8eylenp.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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