mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Vinayak Hegde <vinayakph123@gmail.com>,
	sumit.semwal@linaro.org, gustavo@padovan.org
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v2] Remove the parameter not described warning
Date: Wed, 6 Sep 2023 15:10:37 -0300	[thread overview]
Message-ID: <5e44d344-dee0-027d-4766-01515e6ea155@collabora.com> (raw)
In-Reply-To: <ZPiuH+ghqamtwJGA@vinayak-ubuntu>

Hi Vinayak,

Thanks for you patch

On 06/09/2023 13:51, Vinayak Hegde wrote:
> I encountered a warning during kernel documentation compilation

Usually we write the commit message in imperative mood, please check: 
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes

> due to a missing colon in the documentation for the
> 'num_fences' variable in the sync_file.h header file.
> This change adds the missing colon to align with the documentation format.
> 
> Signed-off-by: Vinayak Hegde <vinayakph123@gmail.com>
> ---
>   include/uapi/linux/sync_file.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/uapi/linux/sync_file.h b/include/uapi/linux/sync_file.h
> index 7e42a5b7558b..b389a5495181 100644
> --- a/include/uapi/linux/sync_file.h
> +++ b/include/uapi/linux/sync_file.h

Since you are modifying this file, if you run:
     git log --oneline include/uapi/linux/sync_file.h
you will notice that almost all changes start with "dma-buf/sync_file:" 
prefix, it would be nice to maintain the style pattern for the commit title.

Regards,
Helen

> @@ -56,7 +56,7 @@ struct sync_fence_info {
>    * @name:	name of fence
>    * @status:	status of fence. 1: signaled 0:active <0:error
>    * @flags:	sync_file_info flags
> - * @num_fences	number of fences in the sync_file
> + * @num_fences: number of fences in the sync_file
>    * @pad:	padding for 64-bit alignment, should always be zero
>    * @sync_fence_info: pointer to array of struct &sync_fence_info with all
>    *		 fences in the sync_file

      parent reply	other threads:[~2023-09-06 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 16:51 Vinayak Hegde
2023-09-06 17:31 ` Sumit Semwal
2023-09-06 18:10 ` Helen Koike [this message]

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=5e44d344-dee0-027d-4766-01515e6ea155@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@padovan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=vinayakph123@gmail.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

all inboxes | Powered by JetHome®