From: Luben Tuikov <luben.tuikov@amd.com>
To: "Russell, Kent" <Kent.Russell@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Quan, Evan" <Evan.Quan@amd.com>,
"Lazar, Lijo" <Lijo.Lazar@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Kasiviswanathan, Harish" <Harish.Kasiviswanathan@amd.com>
Subject: Re: [PATCH 0/5] 0 MHz is not a valid current frequency
Date: Tue, 19 Oct 2021 00:27:15 -0400 [thread overview]
Message-ID: <831e76f9-4fad-da9f-7baf-1e0dc92a378a@amd.com> (raw)
In-Reply-To: <DM6PR12MB3324C490C0CF191F6F34602C85BD9@DM6PR12MB3324.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/html, Size: 62131 bytes --]
next prev parent reply other threads:[~2021-10-19 4:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 3:10 [PATCH 0/5] 0 MHz is not a valid current frequency Luben Tuikov
2021-10-13 3:10 ` [PATCH 1/5] drm/amd/pm: Slight function rename Luben Tuikov
2021-10-13 14:50 ` Russell, Kent
2021-10-13 14:53 ` Luben Tuikov
2021-10-18 22:52 ` Paul Menzel
2021-10-18 23:02 ` Luben Tuikov
2021-10-13 3:10 ` [PATCH 2/5] drm/amd/pm: Rename cur_value to curr_value Luben Tuikov
2021-10-13 3:10 ` [PATCH 3/5] drm/amd/pm: Rename freq_values --> freq_value Luben Tuikov
2021-10-13 3:10 ` [PATCH 4/5] dpm/amd/pm: Sienna: 0 MHz is not a current clock frequency Luben Tuikov
2021-10-13 3:10 ` [PATCH 5/5] dpm/amd/pm: Navi10: " Luben Tuikov
2021-10-13 4:14 ` [PATCH 0/5] 0 MHz is not a valid current frequency Lazar, Lijo
2021-10-13 7:06 ` Quan, Evan
2021-10-13 13:58 ` Alex Deucher
2021-10-13 14:17 ` Lazar, Lijo
2021-10-13 16:22 ` Luben Tuikov
2021-10-13 17:06 ` Lazar, Lijo
2021-10-13 17:19 ` Alex Deucher
2021-10-15 2:25 ` Quan, Evan
2021-10-18 20:19 ` Deucher, Alexander
2021-10-18 20:29 ` Luben Tuikov
2021-10-19 1:04 ` Russell, Kent
2021-10-19 1:06 ` Russell, Kent
2021-10-19 4:27 ` Luben Tuikov [this message]
2021-10-19 13:25 ` Russell, Kent
2021-10-19 13:54 ` Luben Tuikov
2021-10-26 21:26 ` Alex Deucher
2021-10-26 22:00 ` Luben Tuikov
2021-10-27 5:20 ` Lazar, Lijo
2021-10-27 15:12 ` Alex Deucher
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=831e76f9-4fad-da9f-7baf-1e0dc92a378a@amd.com \
--to=luben.tuikov@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Evan.Quan@amd.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=Kent.Russell@amd.com \
--cc=Lijo.Lazar@amd.com \
--cc=amd-gfx@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