From: Greg KH <gregkh@linuxfoundation.org>
To: James Zhu <James.Zhu@amd.com>
Cc: stable@vger.kernel.org, jzhums@gmail.com,
alexander.deucher@amd.com, kolAflash@kolahilft.de
Subject: Re: [PATCH 0/6] Bug:211277 fix backport for 5.10 stable
Date: Fri, 10 Dec 2021 07:33:13 +0100 [thread overview]
Message-ID: <YbL0qYEI6YkBRPLT@kroah.com> (raw)
In-Reply-To: <20211209220956.3466442-1-James.Zhu@amd.com>
On Thu, Dec 09, 2021 at 05:09:50PM -0500, James Zhu wrote:
> These patches are back port for 5.10 stable.
> They are cherry-picked from 5.14 stable.
>
> BugFix: https://bugzilla.kernel.org/show_bug.cgi?id=211277
>
> James Zhu (3):
> drm/amdkfd: separate kfd_iommu_resume from kfd_resume
> drm/amdgpu: add amdgpu_amdkfd_resume_iommu
> drm/amdgpu: move iommu_resume before ip init/resume
>
> Lang Yu (1):
> drm/amd/amdkfd: adjust dummy functions' placement
>
> Yifan Zhang (2):
> drm/amdgpu: init iommu after amdkfd device init
> drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
What has changed from the last time this series was submitted?
thanks,
greg k-h
prev parent reply other threads:[~2021-12-10 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 22:09 [PATCH 0/6] Bug:211277 fix backport for 5.10 stable James Zhu
2021-12-09 22:09 ` [PATCH 1/6] drm/amd/amdkfd: adjust dummy functions' placement James Zhu
2021-12-09 22:09 ` [PATCH 2/6] drm/amdkfd: separate kfd_iommu_resume from kfd_resume James Zhu
2021-12-09 22:09 ` [PATCH 3/6] drm/amdgpu: add amdgpu_amdkfd_resume_iommu James Zhu
2021-12-09 22:09 ` [PATCH 4/6] drm/amdgpu: move iommu_resume before ip init/resume James Zhu
2021-12-09 22:09 ` [PATCH 5/6] drm/amdgpu: init iommu after amdkfd device init James Zhu
2021-12-09 22:09 ` [PATCH 6/6] drm/amdkfd: fix boot failure when iommu is disabled in Picasso James Zhu
2021-12-10 13:33 ` Greg Kroah-Hartman
2021-12-10 14:14 ` James Zhu
2021-12-10 14:35 ` Greg Kroah-Hartman
2021-12-10 14:46 ` James Zhu
2021-12-10 15:12 ` Greg Kroah-Hartman
2021-12-10 15:33 ` James Zhu
2021-12-10 6:33 ` Greg KH [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=YbL0qYEI6YkBRPLT@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=James.Zhu@amd.com \
--cc=alexander.deucher@amd.com \
--cc=jzhums@gmail.com \
--cc=kolAflash@kolahilft.de \
--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.