From: kernel test robot <lkp@intel.com>
To: Ayush Singh <ayushdevel1325@gmail.com>, greybus-dev@lists.linaro.org
Cc: oe-kbuild-all@lists.linux.dev,
Ayush Singh <ayushdevel1325@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org,
Vaishnav M A <vaishnav@beagleboard.org>,
Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH v4 2/3] greybus: Add BeaglePlay Linux Driver
Date: Thu, 7 Sep 2023 05:05:46 +0800 [thread overview]
Message-ID: <202309070423.35kLcJgy-lkp@intel.com> (raw)
In-Reply-To: <20230902182845.1840620-3-ayushdevel1325@gmail.com>
Hi Ayush,
kernel test robot noticed the following build errors:
[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus linus/master v6.5 next-20230906]
[cannot apply to robh/for-next]
[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/Ayush-Singh/dt-bindings-Add-beaglecc1352/20230903-022958
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link: https://lore.kernel.org/r/20230902182845.1840620-3-ayushdevel1325%40gmail.com
patch subject: [PATCH v4 2/3] greybus: Add BeaglePlay Linux Driver
config: microblaze-randconfig-r022-20230907 (https://download.01.org/0day-ci/archive/20230907/202309070423.35kLcJgy-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230907/202309070423.35kLcJgy-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309070423.35kLcJgy-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> drivers/greybus/gb-beagleplay.c:490:1: warning: data definition has no type or storage class
490 | module_serdev_device_driver(gb_beagleplay_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/greybus/gb-beagleplay.c:490:1: error: type defaults to 'int' in declaration of 'module_serdev_device_driver' [-Werror=implicit-int]
>> drivers/greybus/gb-beagleplay.c:490:1: warning: parameter names (without types) in function declaration
>> drivers/greybus/gb-beagleplay.c:481:36: warning: 'gb_beagleplay_driver' defined but not used [-Wunused-variable]
481 | static struct serdev_device_driver gb_beagleplay_driver = {
| ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +490 drivers/greybus/gb-beagleplay.c
480
> 481 static struct serdev_device_driver gb_beagleplay_driver = {
482 .probe = gb_beagleplay_probe,
483 .remove = gb_beagleplay_remove,
484 .driver = {
485 .name = "gb_beagleplay",
486 .of_match_table = of_match_ptr(gb_beagleplay_of_match),
487 },
488 };
489
> 490 module_serdev_device_driver(gb_beagleplay_driver);
491
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-06 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 18:28 [PATCH v4 0/3] greybus: Add BeaglePlay Greybus Driver Ayush Singh
2023-09-02 18:28 ` [PATCH v4 1/3] dt-bindings: Add beaglecc1352 Ayush Singh
2023-09-04 7:14 ` Krzysztof Kozlowski
2023-09-06 16:47 ` Ayush Singh
2023-09-11 6:23 ` Krzysztof Kozlowski
2023-09-02 18:28 ` [PATCH v4 2/3] greybus: Add BeaglePlay Linux Driver Ayush Singh
2023-09-04 7:19 ` Krzysztof Kozlowski
2023-09-05 16:27 ` Ayush Singh
2023-09-06 9:59 ` Krzysztof Kozlowski
2023-09-06 10:33 ` Ayush Singh
2023-09-06 21:05 ` kernel test robot [this message]
2023-09-02 18:28 ` [PATCH v4 3/3] dts: ti: k3-am625-beagleplay: Add beaglecc1352 Ayush Singh
2023-09-04 7:20 ` Krzysztof Kozlowski
2023-09-13 12:57 ` [PATCH v4 0/3] greybus: Add BeaglePlay Greybus Driver Jason Kridner
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=202309070423.35kLcJgy-lkp@intel.com \
--to=lkp@intel.com \
--cc=ayushdevel1325@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vaishnav@beagleboard.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;
as well as URLs for NNTP newsgroup(s).