From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Gene Chen <gene_chen@richtek.com>,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Pavel Machek <pavel@ucw.cz>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v1 1/1] leds: mt6360: Get rid of custom led_init_default_state_get()
Date: Wed, 3 Aug 2022 07:43:06 +0800 [thread overview]
Message-ID: <202208030728.Yo6CynF9-lkp@intel.com> (raw)
In-Reply-To: <20220802212532.7091-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
I love your patch! Yet something to improve:
[auto build test ERROR on pavel-leds/for-next]
[also build test ERROR on linus/master v5.19 next-20220728]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Andy-Shevchenko/leds-mt6360-Get-rid-of-custom-led_init_default_state_get/20220803-052854
base: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
config: arc-randconfig-r043-20220802 (https://download.01.org/0day-ci/archive/20220803/202208030728.Yo6CynF9-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.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://github.com/intel-lab-lkp/linux/commit/260d7c20cbd2b5da92dfa5ffa7c73499661c838f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Andy-Shevchenko/leds-mt6360-Get-rid-of-custom-led_init_default_state_get/20220803-052854
git checkout 260d7c20cbd2b5da92dfa5ffa7c73499661c838f
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash drivers/leds/flash/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/leds/flash/leds-mt6360.c: In function 'mt6360_led_probe':
>> drivers/leds/flash/leds-mt6360.c:832:38: error: implicit declaration of function 'led_init_default_state_get'; did you mean 'led_get_default_pattern'? [-Werror=implicit-function-declaration]
832 | led->default_state = led_init_default_state_get(child);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| led_get_default_pattern
cc1: some warnings being treated as errors
vim +832 drivers/leds/flash/leds-mt6360.c
770
771 static int mt6360_led_probe(struct platform_device *pdev)
772 {
773 struct mt6360_priv *priv;
774 struct fwnode_handle *child;
775 size_t count;
776 int i = 0, ret;
777
778 count = device_get_child_node_count(&pdev->dev);
779 if (!count || count > MT6360_MAX_LEDS) {
780 dev_err(&pdev->dev,
781 "No child node or node count over max led number %zu\n",
782 count);
783 return -EINVAL;
784 }
785
786 priv = devm_kzalloc(&pdev->dev,
787 struct_size(priv, leds, count), GFP_KERNEL);
788 if (!priv)
789 return -ENOMEM;
790
791 priv->leds_count = count;
792 priv->dev = &pdev->dev;
793 mutex_init(&priv->lock);
794
795 priv->regmap = dev_get_regmap(pdev->dev.parent, NULL);
796 if (!priv->regmap) {
797 dev_err(&pdev->dev, "Failed to get parent regmap\n");
798 return -ENODEV;
799 }
800
801 device_for_each_child_node(&pdev->dev, child) {
802 struct mt6360_led *led = priv->leds + i;
803 struct led_init_data init_data = { .fwnode = child, };
804 u32 reg, led_color;
805
806 ret = fwnode_property_read_u32(child, "color", &led_color);
807 if (ret)
808 goto out_flash_release;
809
810 if (led_color == LED_COLOR_ID_RGB ||
811 led_color == LED_COLOR_ID_MULTI)
812 reg = MT6360_VIRTUAL_MULTICOLOR;
813 else {
814 ret = fwnode_property_read_u32(child, "reg", ®);
815 if (ret)
816 goto out_flash_release;
817
818 if (reg >= MT6360_MAX_LEDS) {
819 ret = -EINVAL;
820 goto out_flash_release;
821 }
822 }
823
824 if (priv->leds_active & BIT(reg)) {
825 ret = -EINVAL;
826 goto out_flash_release;
827 }
828 priv->leds_active |= BIT(reg);
829
830 led->led_no = reg;
831 led->priv = priv;
> 832 led->default_state = led_init_default_state_get(child);
833
834 if (reg == MT6360_VIRTUAL_MULTICOLOR ||
835 reg <= MT6360_LED_ISNKML)
836 ret = mt6360_init_isnk_properties(led, &init_data);
837 else
838 ret = mt6360_init_flash_properties(led, &init_data);
839
840 if (ret)
841 goto out_flash_release;
842
843 ret = mt6360_led_register(&pdev->dev, led, &init_data);
844 if (ret)
845 goto out_flash_release;
846
847 i++;
848 }
849
850 platform_set_drvdata(pdev, priv);
851 return 0;
852
853 out_flash_release:
854 mt6360_v4l2_flash_release(priv);
855 return ret;
856 }
857
--
0-DAY CI Kernel Test Service
https://01.org/lkp
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Gene Chen <gene_chen@richtek.com>,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Pavel Machek <pavel@ucw.cz>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v1 1/1] leds: mt6360: Get rid of custom led_init_default_state_get()
Date: Wed, 3 Aug 2022 07:43:06 +0800 [thread overview]
Message-ID: <202208030728.Yo6CynF9-lkp@intel.com> (raw)
In-Reply-To: <20220802212532.7091-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
I love your patch! Yet something to improve:
[auto build test ERROR on pavel-leds/for-next]
[also build test ERROR on linus/master v5.19 next-20220728]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Andy-Shevchenko/leds-mt6360-Get-rid-of-custom-led_init_default_state_get/20220803-052854
base: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
config: arc-randconfig-r043-20220802 (https://download.01.org/0day-ci/archive/20220803/202208030728.Yo6CynF9-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.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://github.com/intel-lab-lkp/linux/commit/260d7c20cbd2b5da92dfa5ffa7c73499661c838f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Andy-Shevchenko/leds-mt6360-Get-rid-of-custom-led_init_default_state_get/20220803-052854
git checkout 260d7c20cbd2b5da92dfa5ffa7c73499661c838f
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash drivers/leds/flash/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/leds/flash/leds-mt6360.c: In function 'mt6360_led_probe':
>> drivers/leds/flash/leds-mt6360.c:832:38: error: implicit declaration of function 'led_init_default_state_get'; did you mean 'led_get_default_pattern'? [-Werror=implicit-function-declaration]
832 | led->default_state = led_init_default_state_get(child);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| led_get_default_pattern
cc1: some warnings being treated as errors
vim +832 drivers/leds/flash/leds-mt6360.c
770
771 static int mt6360_led_probe(struct platform_device *pdev)
772 {
773 struct mt6360_priv *priv;
774 struct fwnode_handle *child;
775 size_t count;
776 int i = 0, ret;
777
778 count = device_get_child_node_count(&pdev->dev);
779 if (!count || count > MT6360_MAX_LEDS) {
780 dev_err(&pdev->dev,
781 "No child node or node count over max led number %zu\n",
782 count);
783 return -EINVAL;
784 }
785
786 priv = devm_kzalloc(&pdev->dev,
787 struct_size(priv, leds, count), GFP_KERNEL);
788 if (!priv)
789 return -ENOMEM;
790
791 priv->leds_count = count;
792 priv->dev = &pdev->dev;
793 mutex_init(&priv->lock);
794
795 priv->regmap = dev_get_regmap(pdev->dev.parent, NULL);
796 if (!priv->regmap) {
797 dev_err(&pdev->dev, "Failed to get parent regmap\n");
798 return -ENODEV;
799 }
800
801 device_for_each_child_node(&pdev->dev, child) {
802 struct mt6360_led *led = priv->leds + i;
803 struct led_init_data init_data = { .fwnode = child, };
804 u32 reg, led_color;
805
806 ret = fwnode_property_read_u32(child, "color", &led_color);
807 if (ret)
808 goto out_flash_release;
809
810 if (led_color == LED_COLOR_ID_RGB ||
811 led_color == LED_COLOR_ID_MULTI)
812 reg = MT6360_VIRTUAL_MULTICOLOR;
813 else {
814 ret = fwnode_property_read_u32(child, "reg", ®);
815 if (ret)
816 goto out_flash_release;
817
818 if (reg >= MT6360_MAX_LEDS) {
819 ret = -EINVAL;
820 goto out_flash_release;
821 }
822 }
823
824 if (priv->leds_active & BIT(reg)) {
825 ret = -EINVAL;
826 goto out_flash_release;
827 }
828 priv->leds_active |= BIT(reg);
829
830 led->led_no = reg;
831 led->priv = priv;
> 832 led->default_state = led_init_default_state_get(child);
833
834 if (reg == MT6360_VIRTUAL_MULTICOLOR ||
835 reg <= MT6360_LED_ISNKML)
836 ret = mt6360_init_isnk_properties(led, &init_data);
837 else
838 ret = mt6360_init_flash_properties(led, &init_data);
839
840 if (ret)
841 goto out_flash_release;
842
843 ret = mt6360_led_register(&pdev->dev, led, &init_data);
844 if (ret)
845 goto out_flash_release;
846
847 i++;
848 }
849
850 platform_set_drvdata(pdev, priv);
851 return 0;
852
853 out_flash_release:
854 mt6360_v4l2_flash_release(priv);
855 return ret;
856 }
857
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-02 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 21:25 [PATCH v1 1/1] leds: mt6360: Get rid of custom led_init_default_state_get() Andy Shevchenko
2022-08-02 21:25 ` Andy Shevchenko
2022-08-02 23:32 ` kernel test robot
2022-08-02 23:32 ` kernel test robot
2022-08-02 23:43 ` kernel test robot [this message]
2022-08-02 23:43 ` kernel test robot
2022-08-03 11:44 ` Matthias Brugger
2022-08-03 11:44 ` Matthias Brugger
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=202208030728.Yo6CynF9-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gene_chen@richtek.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
/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.