From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: [jlayton:kdevops 1/29] checkpatch: ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
Date: Fri, 20 Feb 2026 17:26:27 +0100 [thread overview]
Message-ID: <202602201701.FXb4IBVx-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jeff Layton <jlayton@kernel.org>
Hi Jeff,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git kdevops
head: 5aef1b33e04ec98ed6f4a02ce457ecdc39b794dd
commit: 634702ee55bf1c95e7a3e886d048a4a8f539ccf9 [1/29] vfs: widen inode hash/lookup functions to u64
:::::: branch date: 77 minutes ago
:::::: commit date: 77 minutes ago
reproduce: (https://download.01.org/0day-ci/archive/20260220/202602201701.FXb4IBVx-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#260: FILE: include/linux/fs.h:2954:
+extern struct inode * iget_locked(struct super_block *, u64);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-20 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202602201701.FXb4IBVx-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.