From: Borislav Petkov <bp@alien8.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: RIP: 0010:radeon_vm_fini+0x15/0x220 [radeon]
Date: Mon, 17 Jan 2022 12:21:22 +0100 [thread overview]
Message-ID: <YeVRMvAViydZnMGl@zn.tnic> (raw)
In-Reply-To: <1049939c-422f-787a-7481-21a2598eeedd@amd.com>
On Mon, Jan 17, 2022 at 08:16:09AM +0100, Christian König wrote:
> Interesting to see that even that old stuff is still used.
Well, "used" is a stretch.
This is my way of testing on K8 as pretty much all the big K8 boxes to
which I had access to, got decommissioned so this baby is the only K8
real hw I have now. :-)
Lemme test your patch.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
lkml <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org
Subject: Re: RIP: 0010:radeon_vm_fini+0x15/0x220 [radeon]
Date: Mon, 17 Jan 2022 12:21:22 +0100 [thread overview]
Message-ID: <YeVRMvAViydZnMGl@zn.tnic> (raw)
In-Reply-To: <1049939c-422f-787a-7481-21a2598eeedd@amd.com>
On Mon, Jan 17, 2022 at 08:16:09AM +0100, Christian König wrote:
> Interesting to see that even that old stuff is still used.
Well, "used" is a stretch.
This is my way of testing on K8 as pretty much all the big K8 boxes to
which I had access to, got decommissioned so this baby is the only K8
real hw I have now. :-)
Lemme test your patch.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-17 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 16:11 RIP: 0010:radeon_vm_fini+0x15/0x220 [radeon] Borislav Petkov
2022-01-15 16:11 ` Borislav Petkov
2022-01-17 7:16 ` Christian König
2022-01-17 8:42 ` Jan Stancek
2022-01-17 8:42 ` Jan Stancek
2022-01-17 9:11 ` Christian König
2022-01-17 9:11 ` Christian König
2022-01-17 11:21 ` Borislav Petkov [this message]
2022-01-17 11:21 ` Borislav Petkov
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=YeVRMvAViydZnMGl@zn.tnic \
--to=bp@alien8.de \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@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.