From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [mcgrof-next:20210708-block-fixes-v2 32/89] drivers/block/paride/pd.c:1018:9: error: 'struct gendisk' has no member named 'registered'
Date: Fri, 16 Jul 2021 00:35:53 +0800 [thread overview]
Message-ID: <202107160047.zwcvhhI4-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git 20210708-block-fixes-v2
head: db0174e39de7dc941f158ce53ee3af95b1635b62
commit: 85a77f9a18059a794aa2e33a13f52b73f20dbb08 [32/89] paride/pd: add a registered bool
config: arm-randconfig-r003-20210715 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 10.3.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/mcgrof/linux-next.git/commit/?id=85a77f9a18059a794aa2e33a13f52b73f20dbb08
git remote add mcgrof-next https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git
git fetch --no-tags mcgrof-next 20210708-block-fixes-v2
git checkout 85a77f9a18059a794aa2e33a13f52b73f20dbb08
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=arm 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 >>):
drivers/block/paride/pd.c: In function 'pd_exit':
>> drivers/block/paride/pd.c:1018:9: error: 'struct gendisk' has no member named 'registered'
1018 | if (p->registered)
| ^~
vim +1018 drivers/block/paride/pd.c
1008
1009 static void __exit pd_exit(void)
1010 {
1011 struct pd_unit *disk;
1012 int unit;
1013 unregister_blkdev(major, name);
1014 for (unit = 0, disk = pd; unit < PD_UNITS; unit++, disk++) {
1015 struct gendisk *p = disk->gd;
1016 if (p) {
1017 disk->gd = NULL;
> 1018 if (p->registered)
1019 del_gendisk(p);
1020 blk_cleanup_disk(p);
1021 blk_mq_free_tag_set(&disk->tag_set);
1022 pi_release(disk->pi);
1023 }
1024 }
1025 }
1026
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29571 bytes --]
reply other threads:[~2021-07-15 16:36 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=202107160047.zwcvhhI4-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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®