All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC v6 net-next 6/9] mfd: ocelot: add support for external mfd control over SPI for the VSC7512
Date: Sun, 30 Jan 2022 11:02:31 +0800	[thread overview]
Message-ID: <202201301017.FqxdEjuR-lkp@intel.com> (raw)
In-Reply-To: <20220129220221.2823127-7-colin.foster@in-advantage.com>

Hi Colin,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Colin-Foster/add-support-for-VSC7512-control-over-SPI/20220130-060423
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git ff58831fa02deb42fd731f830d8d9ec545573c7c
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20220130/202201301017.FqxdEjuR-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 33b45ee44b1f32ffdbc995e6fec806271b4b3ba4)
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
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/17c4774323c71c0893e531a24ebf76192cc78fd0
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Colin-Foster/add-support-for-VSC7512-control-over-SPI/20220130-060423
        git checkout 17c4774323c71c0893e531a24ebf76192cc78fd0
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/firmware/xilinx/ drivers/gpu/drm/amd/display/amdgpu_dm/ drivers/mfd/

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

All warnings (new ones prefixed by >>):

>> drivers/mfd/ocelot-core.c:70:16: warning: no previous prototype for function 'ocelot_get_regmap_from_resource' [-Wmissing-prototypes]
   struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
                  ^
   drivers/mfd/ocelot-core.c:70:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
   ^
   static 
   1 warning generated.


vim +/ocelot_get_regmap_from_resource +70 drivers/mfd/ocelot-core.c

    69	
  > 70	struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
    71						       const struct resource *res)
    72	{
    73		struct ocelot_core *core = dev_get_drvdata(dev);
    74	
    75		return ocelot_devm_regmap_init(core, dev, res);
    76	}
    77	EXPORT_SYMBOL(ocelot_get_regmap_from_resource);
    78	

---
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: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v6 net-next 6/9] mfd: ocelot: add support for external mfd control over SPI for the VSC7512
Date: Sun, 30 Jan 2022 11:02:31 +0800	[thread overview]
Message-ID: <202201301017.FqxdEjuR-lkp@intel.com> (raw)
In-Reply-To: <20220129220221.2823127-7-colin.foster@in-advantage.com>

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

Hi Colin,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Colin-Foster/add-support-for-VSC7512-control-over-SPI/20220130-060423
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git ff58831fa02deb42fd731f830d8d9ec545573c7c
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20220130/202201301017.FqxdEjuR-lkp(a)intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 33b45ee44b1f32ffdbc995e6fec806271b4b3ba4)
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
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/17c4774323c71c0893e531a24ebf76192cc78fd0
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Colin-Foster/add-support-for-VSC7512-control-over-SPI/20220130-060423
        git checkout 17c4774323c71c0893e531a24ebf76192cc78fd0
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/firmware/xilinx/ drivers/gpu/drm/amd/display/amdgpu_dm/ drivers/mfd/

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

All warnings (new ones prefixed by >>):

>> drivers/mfd/ocelot-core.c:70:16: warning: no previous prototype for function 'ocelot_get_regmap_from_resource' [-Wmissing-prototypes]
   struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
                  ^
   drivers/mfd/ocelot-core.c:70:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
   ^
   static 
   1 warning generated.


vim +/ocelot_get_regmap_from_resource +70 drivers/mfd/ocelot-core.c

    69	
  > 70	struct regmap *ocelot_get_regmap_from_resource(struct device *dev,
    71						       const struct resource *res)
    72	{
    73		struct ocelot_core *core = dev_get_drvdata(dev);
    74	
    75		return ocelot_devm_regmap_init(core, dev, res);
    76	}
    77	EXPORT_SYMBOL(ocelot_get_regmap_from_resource);
    78	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  parent reply	other threads:[~2022-01-30  3:03 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 22:02 [RFC v6 net-next 0/9] add support for VSC7512 control over SPI Colin Foster
2022-01-29 22:02 ` Colin Foster
2022-01-29 22:02 ` [RFC v6 net-next 1/9] pinctrl: ocelot: allow pinctrl-ocelot to be loaded as a module Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-30  0:30   ` Linus Walleij
2022-01-30  0:30     ` Linus Walleij
2022-01-30 21:30     ` Colin Foster
2022-01-30 21:30       ` Colin Foster
2022-01-31 23:11   ` Florian Fainelli
2022-01-31 23:11     ` Florian Fainelli
2022-01-29 22:02 ` [RFC v6 net-next 2/9] pinctrl: microchip-sgpio: allow sgpio driver to be used " Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-30  0:31   ` Linus Walleij
2022-01-30  0:31     ` Linus Walleij
2022-01-31 23:11   ` Florian Fainelli
2022-01-31 23:11     ` Florian Fainelli
2022-01-31 23:14     ` Colin Foster
2022-01-31 23:14       ` Colin Foster
2022-01-29 22:02 ` [RFC v6 net-next 3/9] net: mdio: mscc-miim: add local dev variable to cleanup probe function Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-31 17:07   ` Vladimir Oltean
2022-01-31 17:07     ` Vladimir Oltean
2022-01-31 23:12   ` Florian Fainelli
2022-01-31 23:12     ` Florian Fainelli
2022-01-29 22:02 ` [RFC v6 net-next 4/9] net: mdio: mscc-miim: add ability to externally register phy reset control Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-30  0:40   ` kernel test robot
2022-01-31 17:13   ` Vladimir Oltean
2022-01-31 17:13     ` Vladimir Oltean
2022-01-31 17:32     ` Colin Foster
2022-01-31 17:32       ` Colin Foster
2022-01-29 22:02 ` [RFC v6 net-next 5/9] mfd: add interface to check whether a device is mfd Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-31  8:47   ` Lee Jones
2022-01-31  8:47     ` Lee Jones
2022-01-29 22:02 ` [RFC v6 net-next 6/9] mfd: ocelot: add support for external mfd control over SPI for the VSC7512 Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-30  2:11   ` kernel test robot
2022-01-30  3:02   ` kernel test robot [this message]
2022-01-30  3:02     ` kernel test robot
2022-01-30  3:33   ` kernel test robot
2022-01-31  9:29   ` Lee Jones
2022-01-31  9:29     ` Lee Jones
2022-01-31 17:29     ` Colin Foster
2022-01-31 17:29       ` Colin Foster
2022-02-01  7:36       ` Lee Jones
2022-02-01  7:36         ` Lee Jones
2022-02-01 17:27         ` Colin Foster
2022-02-01 17:27           ` Colin Foster
2022-01-29 22:02 ` [RFC v6 net-next 7/9] net: mscc: ocelot: expose ocelot wm functions Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-29 22:02 ` [RFC v6 net-next 8/9] net: dsa: felix: add configurable device quirks Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-31 18:15   ` Vladimir Oltean
2022-01-31 18:15     ` Vladimir Oltean
2022-01-29 22:02 ` [RFC v6 net-next 9/9] net: dsa: ocelot: add external ocelot switch control Colin Foster
2022-01-29 22:02   ` Colin Foster
2022-01-31 18:50   ` Vladimir Oltean
2022-01-31 18:50     ` Vladimir Oltean
2022-03-06  0:28     ` Colin Foster
2022-03-06  0:28       ` Colin Foster
2022-03-07 21:51       ` Vladimir Oltean
2022-03-07 21:51         ` Vladimir Oltean
2022-03-08  1:31         ` Colin Foster
2022-03-08  1:31           ` Colin Foster

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=202201301017.FqxdEjuR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=colin.foster@in-advantage.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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.