From: Ashmit Kumar <work.ashmitkumar@gmail.com>
To: gregkh@linuxfoundation.org, mchehab@kernel.org
Cc: linux-staging@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ashmit Kumar <work.ashmitkumar@gmail.com>
Subject: [PATCH v2] staging: media: av7110: remove unnecessary parentheses from return
Date: Tue, 4 Aug 2026 07:49:51 +0000 [thread overview]
Message-ID: <20260804074951.14915-1-work.ashmitkumar@gmail.com> (raw)
The Linux kernel coding style specifies that return is not a function
and therefore parentheses are not required.
Signed-off-by: Ashmit Kumar <work.ashmitkumar@gmail.com>
---
drivers/staging/media/av7110/sp8870.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/av7110/sp8870.c b/drivers/staging/media/av7110/sp8870.c
index 29fb4934c03..83c6ee305d6 100644
--- a/drivers/staging/media/av7110/sp8870.c
+++ b/drivers/staging/media/av7110/sp8870.c
@@ -92,7 +92,7 @@ static int sp8870_readreg(struct sp8870_state *state, u16 reg)
return -1;
}
- return (b1[0] << 8 | b1[1]);
+ return b1[0] << 8 | b1[1];
}
static int sp8870_firmware_upload(struct sp8870_state *state, const struct firmware *fw)
@@ -167,7 +167,7 @@ static void sp8870_microcontroller_start(struct sp8870_state *state)
static int sp8870_read_data_valid_signal(struct sp8870_state *state)
{
- return (sp8870_readreg(state, 0x0D02) > 0);
+ return sp8870_readreg(state, 0x0D02) > 0;
}
static int configure_reg0xc05(struct dtv_frontend_properties *p, u16 *reg0xc05)
--
2.51.0.windows.1
next reply other threads:[~2026-08-04 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 7:49 Ashmit Kumar [this message]
2026-08-04 7:57 ` [PATCH v2] staging: media: av7110: remove unnecessary parentheses from return Greg KH
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=20260804074951.14915-1-work.ashmitkumar@gmail.com \
--to=work.ashmitkumar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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