From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [djwong-xfs:report-refcounts 400/400] fs/xfs/libxfs/xfs_refcount.c:1960:28: warning: Parameter 'low_rec' can be declared with const [constParameter]
Date: Sat, 30 Apr 2022 17:25:23 +0800 [thread overview]
Message-ID: <202204301743.1CbXM5DL-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
CC: "Darrick J. Wong" <darrick.wong@oracle.com>
CC: linux-kernel(a)vger.kernel.org
TO: "Darrick J. Wong" <djwong@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git report-refcounts
head: 0ba96363d9c626afec1bcac75f71e5914adae2a9
commit: 0ba96363d9c626afec1bcac75f71e5914adae2a9 [400/400] xfs: export reference count information to userspace
:::::: branch date: 10 hours ago
:::::: commit date: 10 hours ago
compiler: microblaze-linux-gcc (GCC) 11.3.0
reproduce (cppcheck warning):
# apt-get install cppcheck
git checkout 0ba96363d9c626afec1bcac75f71e5914adae2a9
cppcheck --quiet --enable=style,performance,portability --template=gcc FILE
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_qm_syscalls.c:412:2: warning: Redundant assignment of 'dqp' to itself. [selfAssignment]
xfs_qm_dqrele(dqp);
^
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> fs/xfs/libxfs/xfs_refcount.c:1960:28: warning: Parameter 'low_rec' can be declared with const [constParameter]
struct xfs_refcount_irec *low_rec,
^
>> fs/xfs/libxfs/xfs_refcount.c:1961:28: warning: Parameter 'high_rec' can be declared with const [constParameter]
struct xfs_refcount_irec *high_rec,
^
>> fs/xfs/libxfs/xfs_refcount.c:1216:20: warning: Parameter 'pag' can be declared with const [constParameter]
struct xfs_perag *pag)
^
vim +/low_rec +1960 fs/xfs/libxfs/xfs_refcount.c
0ba96363d9c626 Darrick J. Wong 2022-01-06 1955
0ba96363d9c626 Darrick J. Wong 2022-01-06 1956 /* Find all refcount records between two keys. */
0ba96363d9c626 Darrick J. Wong 2022-01-06 1957 int
0ba96363d9c626 Darrick J. Wong 2022-01-06 1958 xfs_refcount_query_range(
0ba96363d9c626 Darrick J. Wong 2022-01-06 1959 struct xfs_btree_cur *cur,
0ba96363d9c626 Darrick J. Wong 2022-01-06 @1960 struct xfs_refcount_irec *low_rec,
0ba96363d9c626 Darrick J. Wong 2022-01-06 @1961 struct xfs_refcount_irec *high_rec,
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-30 9:25 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=202204301743.1CbXM5DL-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 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.