mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hanyu001@208suo.com
To: mchehab@kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Cc: linux-media@vger.kernel.org
Subject: [PATCH] wifi: av7110: remove space before ')'
Date: Tue, 18 Jul 2023 15:27:58 +0800	[thread overview]
Message-ID: <89948b0041b6553b65a8cf8e8f1152b4@208suo.com> (raw)
In-Reply-To: <tencent_C61A29FA864A05D9D83277F0CF7721A52D0A@qq.com>

The patch fixes the following errors detected by checkpatch.pl:

./drivers/staging/media/av7110/av7110.c:2556: ERROR: space prohibited 
before that close parenthesis ')'
./drivers/staging/media/av7110/av7110.c:2558: ERROR: space prohibited 
before that close parenthesis ')'
./drivers/staging/media/av7110/av7110.c:2599: ERROR: space prohibited 
before that close parenthesis ')'

Signed-off-by: Yu Han <hanyu001@208suo.com>
---
  drivers/staging/media/av7110/av7110.c | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/media/av7110/av7110.c 
b/drivers/staging/media/av7110/av7110.c
index a5a431c1..6b9df2c 100644
--- a/drivers/staging/media/av7110/av7110.c
+++ b/drivers/staging/media/av7110/av7110.c
@@ -2553,9 +2553,9 @@ static int av7110_attach(struct saa7146_dev* dev,
           * use 0x03 to track RPS1 interrupts - increase by 1 every 
gpio3 is toggled
           * use 0x15 to track VPE  interrupts - increase by 1 every 
vpeirq() is called
           */
-        saa7146_write(dev, EC1SSR, (0x03<<2) | 3 );
+        saa7146_write(dev, EC1SSR, (0x03<<2) | 3);
          /* set event counter 1 threshold to maximum allowed value       
  (rEC p55) */
-        saa7146_write(dev, ECT1R,  0x3fff );
+        saa7146_write(dev, ECT1R,  0x3fff);
  #endif
          /* Setup BUDGETPATCH MAIN RPS1 "program" (p35) */
          count = 0;
@@ -2596,7 +2596,7 @@ static int av7110_attach(struct saa7146_dev* dev,
           * then RPS_THRESH1 should be set to trigger
           * every TS_HEIGHT (512) lines.
           */
-        saa7146_write(dev, RPS_THRESH1, (TS_HEIGHT*1) | MASK_12 );
+        saa7146_write(dev, RPS_THRESH1, (TS_HEIGHT*1) | MASK_12);

          /* Enable RPS1                                                  
(rFC p33) */
          saa7146_write(dev, MC1, (MASK_13 | MASK_29));

       reply	other threads:[~2023-07-18  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_C61A29FA864A05D9D83277F0CF7721A52D0A@qq.com>
2023-07-18  7:27 ` hanyu001 [this message]
2023-07-18 13:32   ` 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=89948b0041b6553b65a8cf8e8f1152b4@208suo.com \
    --to=hanyu001@208suo.com \
    --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

all inboxes | Powered by JetHome®