All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [nvdimm:libnvdimm-pending 5/29] drivers/nvdimm/namespace_devs.c:1651:3: error: 'nd_device_attribute_group' undeclared here (not in a function); did you mean 'nd_namespace_attribute_group'?
Date: Thu, 07 Nov 2019 22:05:11 +0800	[thread overview]
Message-ID: <201911072208.INQbaKdY%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2691 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git libnvdimm-pending
head:   1065342bfccac9be6ff3aa1874e1b8d32c0b4603
commit: a0ac861e5cfc7fc79bf63a08632e872cfa07510a [5/29] libnvdimm: Move nd_region_attribute_group to device_type
config: x86_64-randconfig-c001-201944 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
        git checkout a0ac861e5cfc7fc79bf63a08632e872cfa07510a
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/nvdimm/namespace_devs.c:1651:3: error: 'nd_device_attribute_group' undeclared here (not in a function); did you mean 'nd_namespace_attribute_group'?
     &nd_device_attribute_group,
      ^~~~~~~~~~~~~~~~~~~~~~~~~
      nd_namespace_attribute_group
   drivers/nvdimm/namespace_devs.c:1653:3: error: 'nd_numa_attribute_group' undeclared here (not in a function); did you mean 'nvdimm_attribute_group'?
     &nd_numa_attribute_group,
      ^~~~~~~~~~~~~~~~~~~~~~~
      nvdimm_attribute_group
--
>> drivers/nvdimm/btt_devs.c:165:3: error: 'nd_device_attribute_group' undeclared here (not in a function); did you mean 'nd_btt_attribute_group'?
     &nd_device_attribute_group,
      ^~~~~~~~~~~~~~~~~~~~~~~~~
      nd_btt_attribute_group
   drivers/nvdimm/btt_devs.c:166:3: error: 'nd_numa_attribute_group' undeclared here (not in a function); did you mean 'nd_btt_attribute_group'?
     &nd_numa_attribute_group,
      ^~~~~~~~~~~~~~~~~~~~~~~
      nd_btt_attribute_group

vim +1651 drivers/nvdimm/namespace_devs.c

3d88002e4a7bd4 Dan Williams 2015-05-31  1649  
3d88002e4a7bd4 Dan Williams 2015-05-31  1650  static const struct attribute_group *nd_namespace_attribute_groups[] = {
3d88002e4a7bd4 Dan Williams 2015-05-31 @1651  	&nd_device_attribute_group,
3d88002e4a7bd4 Dan Williams 2015-05-31  1652  	&nd_namespace_attribute_group,
74ae66c3b14ffa Toshi Kani   2015-06-19  1653  	&nd_numa_attribute_group,
3d88002e4a7bd4 Dan Williams 2015-05-31  1654  	NULL,
3d88002e4a7bd4 Dan Williams 2015-05-31  1655  };
3d88002e4a7bd4 Dan Williams 2015-05-31  1656  

:::::: The code at line 1651 was first introduced by commit
:::::: 3d88002e4a7bd40f355550284c6cd140e6fe29dc libnvdimm: support for legacy (non-aliasing) nvdimms

:::::: TO: Dan Williams <dan.j.williams@intel.com>
:::::: CC: Dan Williams <dan.j.williams@intel.com>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32509 bytes --]

                 reply	other threads:[~2019-11-07 14:05 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=201911072208.INQbaKdY%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@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.