public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Bergh <bergh.jonathan@gmail.com>
To: mchehab@kernel.org
Cc: mcgrof@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jonathan Bergh <bergh.jonathan@gmail.com>
Subject: [PATCH 0/9] staging: media: av7110: These patches address various code style and formatting issues in the av7110 driver
Date: Sun,  3 Mar 2024 20:20:31 +0100	[thread overview]
Message-ID: <20240303192040.8116-1-bergh.jonathan@gmail.com> (raw)

The following patches fix a number of code style issues identified by
checkpatch in the av7110 driver.

Jonathan Bergh (9):
  staging: media: av7110: Fix formatting problem where trailing statements
    should be on a new line
  staging: media: av7110: Remove braces for single line statement blocks
  staging: media: av7110: Remove spaces between function name and
    opening parenthesis
  staging: media: av7110: Fix formatting of pointers to meet coding
    style guidelines
  staging: media: av7110: Fix block comments to meet code style
    guidelines
  staging: media: av7110: Remove extra whitespace before opening '['s
  staging: media: av7110: Remove extra whitespace before ','
  staging: media: av7110: Ensure whitespace ahead of opening brace '{'
  staging: media: av7110: Ensure newline after variable declarations

 drivers/staging/media/av7110/sp8870.c | 136 +++++++++++++-------------
 1 file changed, 70 insertions(+), 66 deletions(-)

-- 
2.40.1


             reply	other threads:[~2024-03-03 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 19:20 Jonathan Bergh [this message]
2024-03-03 19:20 ` [PATCH 1/9] staging: media: av7110: Fix formatting problem where trailing statements should be on a new line Jonathan Bergh
2024-03-03 19:20 ` [PATCH 2/9] staging: media: av7110: Remove braces for single line statement blocks Jonathan Bergh
2024-03-03 19:20 ` [PATCH 3/9] staging: media: av7110: Remove spaces between function name and opening parenthesis Jonathan Bergh
2024-03-03 19:20 ` [PATCH 4/9] staging: media: av7110: Fix formatting of pointers to meet coding style guidelines Jonathan Bergh
2024-03-03 19:20 ` [PATCH 5/9] staging: media: av7110: Fix block comments to meet code " Jonathan Bergh
2024-03-03 19:20 ` [PATCH 6/9] staging: media: av7110: Remove extra whitespace before opening '['s Jonathan Bergh
2024-03-03 19:20 ` [PATCH 7/9] staging: media: av7110: Remove extra whitespace before ',' Jonathan Bergh
2024-03-03 19:20 ` [PATCH 8/9] staging: media: av7110: Ensure whitespace ahead of opening brace '{' Jonathan Bergh
2024-03-03 19:20 ` [PATCH 9/9] staging: media: av7110: Ensure newline after variable declarations Jonathan Bergh
2024-04-24  9:34 ` [PATCH 0/9] staging: media: av7110: These patches address various code style and formatting issues in the av7110 driver Hans Verkuil

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=20240303192040.8116-1-bergh.jonathan@gmail.com \
    --to=bergh.jonathan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    /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