From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Krister Johansen" <kjlx@templeofstupid.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fuse submount_lookup needs to be initialized
Date: Mon, 13 Nov 2023 19:23:04 -0000 [thread overview]
Message-ID: <169990338428.24211.5227530969920814866@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1699564053.git.kjlx@templeofstupid.com>
== Series Details ==
Series: Fuse submount_lookup needs to be initialized
URL : https://patchwork.freedesktop.org/series/126336/
State : warning
== Summary ==
Error: dim checkpatch failed
919b794dcf31 fuse: ensure submount_lookup is initialized on alloc
75bb4ac3057d fuse: share lookup state between submount and its parent
-:41: WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#41: FILE: fs/fuse/fuse_i.h:72:
+ * and kernel */
-:72: CHECK:ALLOC_SIZEOF_STRUCT: Prefer kzalloc(sizeof(*sl)...) over kzalloc(sizeof(struct fuse_submount_lookup)...)
#72: FILE: fs/fuse/inode.c:75:
+ sl = kzalloc(sizeof(struct fuse_submount_lookup), GFP_KERNEL_ACCOUNT);
total: 0 errors, 1 warnings, 1 checks, 163 lines checked
next prev parent reply other threads:[~2023-11-13 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 22:36 [PATCH 0/2] Fuse submount_lookup needs to be initialized Krister Johansen
2023-11-09 22:36 ` [Intel-gfx] " Krister Johansen
2023-11-09 22:37 ` [PATCH 1/2] fuse: ensure submount_lookup is initialized on alloc Krister Johansen
2023-11-09 22:37 ` [Intel-gfx] " Krister Johansen
2023-11-09 22:37 ` [v5 PATCH 2/2] fuse: share lookup state between submount and its parent Krister Johansen
2023-11-09 22:37 ` [Intel-gfx] " Krister Johansen
2023-11-10 9:44 ` [PATCH 0/2] Fuse submount_lookup needs to be initialized Miklos Szeredi
2023-11-10 9:44 ` [Intel-gfx] " Miklos Szeredi
2023-11-13 19:23 ` Patchwork [this message]
2023-11-13 19:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-14 0:57 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=169990338428.24211.5227530969920814866@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kjlx@templeofstupid.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.