Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Randhawa, Jagmeet" <jagmeet.randhawa@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	<igt-dev@lists.freedesktop.org>, <jonathan.cavitt@intel.com>
Subject: Re: [PATCH i-g-t] lib/xe/xe_spin.c: Fix typo
Date: Wed, 8 May 2024 11:56:21 -0700	[thread overview]
Message-ID: <7fe4cd1a-dfe2-4113-8afa-6a092e6c737a@intel.com> (raw)
In-Reply-To: <20240508142255.jo6pmyrpbzvbqtdh@kamilkon-DESK.igk.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]


On 5/8/2024 7:22 AM, Kamil Konieczny wrote:
> Hi Jagmeet,
> On 2024-05-07 at 12:23:12 -0700, Jagmeet Randhawa wrote:
>> Fix typos to follow proper format.
> While at it could you also rephrase it somewhat?
> See below, no need for sending new version, just
> reply in this thread.
>
> After agreement I could merge it with ack from Jonathan.
>
>> Cc: Jonathan Cavitt<jonathan.cavitt@intel.com>
>> Signed-off-by: Jagmeet Randhawa<jagmeet.randhawa@intel.com>
>> ---
>>   lib/xe/xe_spin.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/lib/xe/xe_spin.c b/lib/xe/xe_spin.c
>> index 381e5e950..2dbd51199 100644
>> --- a/lib/xe/xe_spin.c
>> +++ b/lib/xe/xe_spin.c
>> @@ -162,7 +162,7 @@ void xe_spin_init(struct xe_spin *spin, struct xe_spin_opts *opts)
>>    * xe_spin_started:
>>    * @spin: pointer to spinner mapped bo
>>    *
>> - * Returns: true if spinner is running, othwerwise false.
>> + * Returns: true if spinner is running, otherwise false.
>>    */
>>   bool xe_spin_started(struct xe_spin *spin)
>>   {
>> @@ -262,8 +262,8 @@ void xe_spin_sync_wait(int fd, struct igt_spin *spin)
>>    * xe_spin_free:
>>    * @spin: spin state from igt_spin_new()
>>    *
>> - * Wrapper to free spinner whhich is triggered by xe_spin_create.
>> - * which distroys vm, exec_queue and unbinds the vm which is binded to
>> + * Wrapper to free spinner which is triggered by xe_spin_create.
>> + * which destroys vm, exec_queue and unbinds the vm which is binded to
> imho better would be:
>
>   * Wrapper to free spinner created by xe_spin_create. It will
>   * destroy vm, exec_queue and unbind the vm which was binded to
>
> What you think? Jonathan? Btw 'triggered by' could stay, no strong
> opinion for 'created by'.
>
> Regards,
> Kamil
Hey Kamil, I agree with you. Your description is more clean. I think

'created by' is a better fit.  If Jonathan is in agreement, we should also

change the subject to "[PATCH i-g-t] lib/xe/xe_spin: Improve comments 
and fix typos"

as you mentioned.


>>    * the exec_queue and bo.
>>    *
>>    */
>> -- 
>> 2.25.1
>>

[-- Attachment #2: Type: text/html, Size: 8742 bytes --]

  reply	other threads:[~2024-05-08 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 19:23 [PATCH i-g-t] lib/xe/xe_spin.c: Fix typo Jagmeet Randhawa
2024-05-07 20:01 ` Cavitt, Jonathan
2024-05-07 20:50 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-05-07 22:42 ` ✓ CI.xeBAT: " Patchwork
2024-05-08  4:34 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-08  8:51 ` ✗ CI.xeFULL: " Patchwork
2024-05-08 19:00   ` Randhawa, Jagmeet
2024-05-08 14:22 ` [PATCH i-g-t] " Kamil Konieczny
2024-05-08 18:56   ` Randhawa, Jagmeet [this message]
2024-05-08 14:33 ` Kamil Konieczny

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=7fe4cd1a-dfe2-4113-8afa-6a092e6c737a@intel.com \
    --to=jagmeet.randhawa@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=kamil.konieczny@linux.intel.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