From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jlayton:ceph-sparse-read 14/15] net/ceph/osd_client.c:5847:50: error: incompatible types when initializing type 'struct ceph_sparse_extent *' using type 'struct ceph_sparse_extent'
Date: Sat, 19 Mar 2022 04:18:43 +0800 [thread overview]
Message-ID: <202203190457.rN00jXWd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git ceph-sparse-read
head: dd42d5af0df78fdd04a5a93c0488211435bd32e6
commit: 555a255575736e3b39f6b2c70574422439b765b6 [14/15] libceph: add sparse read support to OSD client
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20220319/202203190457.rN00jXWd-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/commit/?id=555a255575736e3b39f6b2c70574422439b765b6
git remote add jlayton https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
git fetch --no-tags jlayton ceph-sparse-read
git checkout 555a255575736e3b39f6b2c70574422439b765b6
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/ceph/osd_client.c: In function 'convert_extent_map':
>> net/ceph/osd_client.c:5847:50: error: incompatible types when initializing type 'struct ceph_sparse_extent *' using type 'struct ceph_sparse_extent'
5847 | struct ceph_sparse_extent *ext = sr->sr_extent[i];
| ^~
vim +5847 net/ceph/osd_client.c
5840
5841 #ifdef __BIG_ENDIAN
5842 static inline void convert_extent_map(struct ceph_sparse_read *sr)
5843 {
5844 int i;
5845
5846 for (i = 0; i < sr->sr_count; i++) {
> 5847 struct ceph_sparse_extent *ext = sr->sr_extent[i];
5848
5849 ext->off = le64_to_cpu((__force __le32)ext->off);
5850 ext->len = le64_to_cpu((__force __le32)ext->len);
5851 }
5852 }
5853 #else
5854 static inline void convert_extent_map(struct ceph_sparse_read *sr)
5855 {
5856 }
5857 #endif
5858
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-18 20:18 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=202203190457.rN00jXWd-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®