public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Paul Lawrence <[email protected]>
Cc: [email protected],
	GNU/Weeb Mailing List <[email protected]>,
	[email protected]
Subject: [PATCH] ANDROID: fuse-bpf: fix semicolon.cocci warnings
Date: Thu, 10 Mar 2022 02:10:59 +0800	[thread overview]
Message-ID: <20220309181059.GA31901@06428da54493> (raw)
In-Reply-To: <[email protected]>

From: kernel test robot <[email protected]>

fs/fuse/dir.c:557:43-44: Unneeded semicolon


 Remove unneeded semicolon.

Generated by: scripts/coccinelle/misc/semicolon.cocci

Fixes: 8efdff35e305 ("ANDROID: fuse-bpf: Move fd operations to be synchronous")
Reported-by: kernel test robot <[email protected]>
Signed-off-by: kernel test robot <[email protected]>
---

tree:   https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android13-5.10
head:   681ba23265bee4f2f0bd461df7d0025f4df17f09
commit: 8efdff35e3052e44d519ccfb9d50594f5df0240b [9996/9999] ANDROID: fuse-bpf: Move fd operations to be synchronous
:::::: branch date: 8 hours ago
:::::: commit date: 22 hours ago

 fs/fuse/dir.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -554,7 +554,7 @@ int fuse_lookup_name(struct super_block
 			struct bpf_prog *bpf_prog = ERR_PTR(-EINVAL);
 
 			if (bpf_file && !IS_ERR(bpf_file))
-				bpf_prog = fuse_get_bpf_prog(bpf_file);;
+				bpf_prog = fuse_get_bpf_prog(bpf_file);
 
 			if (IS_ERR(bpf_prog)) {
 				iput(*inode);

      reply	other threads:[~2022-03-09 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 18:12 [ammarfaizi2-block:google/android/kernel/common/android13-5.10 9996/9999] fs/fuse/dir.c:557:43-44: Unneeded semicolon kernel test robot
2022-03-09 18:10 ` kernel test robot [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=20220309181059.GA31901@06428da54493 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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