From: Julia Lawall <julia.lawall@inria.fr>
To: Aliya Rahmani <aliyarahmani786@gmail.com>
Cc: mchehab@kernel.org, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, outreachy@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: media: av7110: comparison to NULL could be written "fe_func"
Date: Mon, 18 Apr 2022 20:22:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204182018480.13551@hadrien> (raw)
In-Reply-To: <20220418180859.18488-1-aliyarahmani786@gmail.com>
On Mon, 18 Apr 2022, Aliya Rahmani wrote:
> Fixed coding style for null comparisons to be more
> consistent with the rest of the kernel coding style.
The log message (both the subject line and the text just above) should be
in the imperative. Typically, that means that you should not be using
verbs that end in "ed".
There is too much detail in the subject line. Consider how you could give
the general idea, but be more concise.
For the text above, what could you say rather than "fix". When you say
that you fixed something, the reader may know (or at least hope) that it
is better, but gets no information about what you did, nor why.
julia
>
> Signed-off-by: Aliya Rahmani <aliyarahmani786@gmail.com>
> ---
> drivers/staging/media/av7110/av7110.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/av7110/av7110.c b/drivers/staging/media/av7110/av7110.c
> index d74ee0ecfb36..bdc6adf70d72 100644
> --- a/drivers/staging/media/av7110/av7110.c
> +++ b/drivers/staging/media/av7110/av7110.c
> @@ -107,7 +107,7 @@ static int av7110_num;
>
> #define FE_FUNC_OVERRIDE(fe_func, av7110_copy, av7110_func) \
> {\
> - if (fe_func != NULL) { \
> + if (fe_func) { \
> av7110_copy = fe_func; \
> fe_func = av7110_func; \
> } \
> --
> 2.25.1
>
>
>
prev parent reply other threads:[~2022-04-18 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 18:09 [PATCH] staging: media: av7110: comparison to NULL could be written "fe_func" Aliya Rahmani
2022-04-18 18:22 ` Julia Lawall [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=alpine.DEB.2.22.394.2204182018480.13551@hadrien \
--to=julia.lawall@inria.fr \
--cc=aliyarahmani786@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=outreachy@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