Linux kernel staging patches
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Aliya Rahmani <aliyarahmani786@gmail.com>
Cc: clabbe@baylibre.com, gregkh@linuxfoundation.org,
	 linux-staging@lists.linux.dev, outreachy@lists.linux.dev,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] staging: media: zoran: fix warnings reported by checkpatch
Date: Mon, 18 Apr 2022 18:40:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2204181839370.13551@hadrien> (raw)
In-Reply-To: <20220418162244.15346-1-aliyarahmani786@gmail.com>



On Mon, 18 Apr 2022, Aliya Rahmani wrote:

> These patches address style issues found by checkpatch in the
> zoran/videocodec.c file.
>
> changes since v1: Rework commit description and subject.

The change description is not very specific.  Does it affect all of the
patches, or are some unchanged?

julia

>
> Aliya Rahmani (3):
>  staging: media: zoran: use seq_puts() instead of seq_printf()
>  staging: media: zoran: else is not generally useful after a break or return
>  staging: media: zoran: avoid macro argument precedence issues
>
> drivers/staging/media/zoran/videocodec.c | 9++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
>
> --
> 2.25.1
>
>
>

      parent reply	other threads:[~2022-04-18 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 16:22 [PATCH v2 0/3] staging: media: zoran: fix warnings reported by checkpatch Aliya Rahmani
2022-04-18 16:22 ` [PATCH v2 1/3] staging: media: zoran: use seq_puts() instead of seq_printf() Aliya Rahmani
2022-04-18 16:22 ` [PATCH v2 2/3] staging: media: zoran: else is not generally useful after a break or return Aliya Rahmani
2022-04-18 16:37   ` Julia Lawall
2022-04-18 16:22 ` [PATCH v2 3/3] staging: media: zoran: add parentheses on macro parameter Aliya Rahmani
2022-04-18 16:40 ` 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.2204181839370.13551@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=aliyarahmani786@gmail.com \
    --cc=clabbe@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --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