From: kbuild test robot <lkp@intel.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: kbuild-all@lists.01.org, linux-xfs@vger.kernel.org,
Chandan Babu R <chandanrlinux@gmail.com>,
Christoph Hellwig <hch@lst.de>
Subject: [xfs-linux:xfs-5.8-merge 57/94] WARNING: __func__ should be used instead of gcc specific __FUNCTION__
Date: Mon, 18 May 2020 12:06:47 +0800 [thread overview]
Message-ID: <20200518040647.GD24805@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs-5.8-merge
head: dc6a7f69e533f64cae2d01d7acf82075e65f543d
commit: 3ec6efa703cf65887e681d1f97d38a63261d907e [57/94] xfs: refactor log recovery icreate item dispatch for pass2 commit functions
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
scripts/checkpatch.pl 0001-xfs-refactor-log-recovery-icreate-item-dispatch-for-.patch
# many are suggestions rather than must-fix
WARNING: __func__ should be used instead of gcc specific __FUNCTION__
#119: fs/xfs/xfs_icreate_item.c:204:
+ "%s: unsupported chunk length", __FUNCTION__);
WARNING: __func__ should be used instead of gcc specific __FUNCTION__
#127: fs/xfs/xfs_icreate_item.c:212:
+ __FUNCTION__);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [xfs-linux:xfs-5.8-merge 57/94] WARNING: __func__ should be used instead of gcc specific __FUNCTION__
Date: Mon, 18 May 2020 12:06:47 +0800 [thread overview]
Message-ID: <20200518040647.GD24805@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
tree: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs-5.8-merge
head: dc6a7f69e533f64cae2d01d7acf82075e65f543d
commit: 3ec6efa703cf65887e681d1f97d38a63261d907e [57/94] xfs: refactor log recovery icreate item dispatch for pass2 commit functions
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
scripts/checkpatch.pl 0001-xfs-refactor-log-recovery-icreate-item-dispatch-for-.patch
# many are suggestions rather than must-fix
WARNING: __func__ should be used instead of gcc specific __FUNCTION__
#119: fs/xfs/xfs_icreate_item.c:204:
+ "%s: unsupported chunk length", __FUNCTION__);
WARNING: __func__ should be used instead of gcc specific __FUNCTION__
#127: fs/xfs/xfs_icreate_item.c:212:
+ __FUNCTION__);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2020-05-18 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 4:06 kbuild test robot [this message]
2020-05-18 4:06 ` [xfs-linux:xfs-5.8-merge 57/94] WARNING: __func__ should be used instead of gcc specific __FUNCTION__ kbuild test robot
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=20200518040647.GD24805@intel.com \
--to=lkp@intel.com \
--cc=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-xfs@vger.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 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.