From: Thorsten Leemhuis <linux@leemhuis.info>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Evan Quan <evan.quan@amd.com>
Cc: amd-gfx@lists.freedesktop.org, Alexander.Deucher@amd.com,
arthur.marsh@internode.on.net, regressions@lists.linux.dev
Subject: Re: [PATCH] drm/amd/pm: fix the deadlock issue observed on SI
Date: Mon, 11 Apr 2022 10:30:57 +0200 [thread overview]
Message-ID: <5d7ac2a0-00b7-1307-6aeb-1461c79bd6f8@leemhuis.info> (raw)
In-Reply-To: <78cdd8a2-4482-7b1b-2df4-a2983c1b2887@molgen.mpg.de>
On 11.04.22 09:59, Paul Menzel wrote:
> Am 11.04.22 um 09:47 schrieb Evan Quan:
>
> As it’s a regression, please follow the documentation, and add the
> related tags.
Yes please, otherwise you break tools that reply on this, like my
regression tracking efforts.
> Fixes: 3712e7a49459 ("drm/amd/pm: unified lock protections in
> amdgpu_dpm.c")
> Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Reported-by: Arthur Marsh <arthur.marsh@internode.on.net>
> Link:
> https://lore.kernel.org/r/9e689fea-6c69-f4b0-8dee-32c4cf7d8f9c@molgen.mpg.de
> BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1957
>
> Also add the link from Arthur.
What is BugLink? That is not in the kernel's documentation afaics (BTW,
as other people use it as wll: where does that actually come from?
GitLab?) . It should just be "Link:". Or am I missing something?
Ciao, Thorsten
next prev parent reply other threads:[~2022-04-11 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411074732.36486-1-evan.quan@amd.com>
2022-04-11 7:59 ` [PATCH] drm/amd/pm: fix the deadlock issue observed on SI Paul Menzel
2022-04-11 8:30 ` Thorsten Leemhuis [this message]
2022-04-11 8:55 ` Quan, Evan
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=5d7ac2a0-00b7-1307-6aeb-1461c79bd6f8@leemhuis.info \
--to=linux@leemhuis.info \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arthur.marsh@internode.on.net \
--cc=evan.quan@amd.com \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).