AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben.tuikov@amd.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Alex Deucher <Alexander.Deucher@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/amd/pm: Slight function rename
Date: Mon, 18 Oct 2021 19:02:32 -0400	[thread overview]
Message-ID: <e2b793d0-d7df-ad02-c239-a0165c4f9abc@amd.com> (raw)
In-Reply-To: <580a9f54-1cbc-27b0-f5d8-05db2180b69a@molgen.mpg.de>

Okay, no problem--I'll add a verb there and resend the patch set. Thanks for letting me know.

Regards,
Luben

On 2021-10-18 18:52, Paul Menzel wrote:
> Dear Luben,
>
>
> Am 13.10.21 um 05:10 schrieb Luben Tuikov:
>
> […]
>
> A small nit regarding the subject. It’d be great if you made it a 
> statement by adding a verb (in imperative mood). git standard messages 
> are doing the same with *Merge …* and *Revert …*.
>
>
> Kind regards,
>
> Paul


  reply	other threads:[~2021-10-18 23:02 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 [this message]
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
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=e2b793d0-d7df-ad02-c239-a0165c4f9abc@amd.com \
    --to=luben.tuikov@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=pmenzel@molgen.mpg.de \
    /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