From: "Christian König" <christian.koenig@amd.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
"Chen, Guchun" <Guchun.Chen@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ttm: check null pointer before accessing when swapping
Date: Thu, 27 Jul 2023 10:11:24 +0200 [thread overview]
Message-ID: <54d642a4-d8ad-e626-0fe1-4254aa0708da@amd.com> (raw)
In-Reply-To: <CABXGCsM_cLPLBJW4Kxk3RBn9UpsMDqLA8bhEOOVyDSERcO-WMw@mail.gmail.com>
Am 27.07.23 um 09:39 schrieb Mikhail Gavrilov:
> On Thu, Jul 27, 2023 at 12:33 PM Chen, Guchun <Guchun.Chen@amd.com> wrote:
>>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>>
>>> Has this already been pushed to drm-misc-next?
>>>
>>> Thanks,
>>> Christian.
>> Not yet, Christian, as I don't have push permission. I saw you were on vacation, so I would expect to ping you to push after you are back with full recharge.
> I expect to see it in drm-fixes-6.5 cause the problem appeared during
> the 6.5 release cycle.
Good point. The patch introducing the problem had a CC: stable tag as well.
So I've added the appropriate tags and pushed it to drm-misc-fixes.
Thanks,
Christian.
> And yes, I follow all pull requests. This patch was not included in
> yesterday's pull request :(
prev parent reply other threads:[~2023-07-27 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 2:42 [PATCH] drm/ttm: check null pointer before accessing when swapping Guchun Chen
2023-07-24 13:36 ` Alex Deucher
2023-07-27 7:28 ` Christian König
2023-07-27 7:33 ` Chen, Guchun
2023-07-27 7:39 ` Mikhail Gavrilov
2023-07-27 8:11 ` Christian König [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=54d642a4-d8ad-e626-0fe1-4254aa0708da@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Guchun.Chen@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mikhail.v.gavrilov@gmail.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