From: kernel test robot <lkp@intel.com>
To: Rosen Penev <rosenp@gmail.com>, linux-wireless@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Stanislaw Gruszka <stf_xl@wp.pl>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCHv2 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc
Date: Wed, 9 Jul 2025 17:30:36 +0800 [thread overview]
Message-ID: <202507091735.YeYeU2tw-lkp@intel.com> (raw)
In-Reply-To: <20250708201745.5900-5-rosenp@gmail.com>
Hi Rosen,
kernel test robot noticed the following build errors:
[auto build test ERROR on wireless/main]
[also build test ERROR on next-20250708]
[cannot apply to wireless-next/main robh/for-next linus/master v6.16-rc5]
[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/Rosen-Penev/wifi-rt2x00-add-COMPILE_TEST/20250709-042051
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git main
patch link: https://lore.kernel.org/r/20250708201745.5900-5-rosenp%40gmail.com
patch subject: [PATCHv2 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250709/202507091735.YeYeU2tw-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250709/202507091735.YeYeU2tw-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/202507091735.YeYeU2tw-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/wireless/ralink/rt2x00/rt2800soc.c:376:27: error: 'rt2x00soc_suspend' undeclared here (not in a function); did you mean 'rt2x00lib_suspend'?
376 | .suspend = rt2x00soc_suspend,
| ^~~~~~~~~~~~~~~~~
| rt2x00lib_suspend
>> drivers/net/wireless/ralink/rt2x00/rt2800soc.c:377:27: error: 'rt2x00soc_resume' undeclared here (not in a function); did you mean 'rt2x00soc_remove'?
377 | .resume = rt2x00soc_resume,
| ^~~~~~~~~~~~~~~~
| rt2x00soc_remove
vim +376 drivers/net/wireless/ralink/rt2x00/rt2800soc.c
90ce325a735fa7 drivers/net/wireless/ralink/rt2x00/rt2800soc.c Rosen Penev 2025-07-08 368
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 369 static struct platform_driver rt2800soc_driver = {
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 370 .driver = {
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 371 .name = "rt2800_wmac",
90ce325a735fa7 drivers/net/wireless/ralink/rt2x00/rt2800soc.c Rosen Penev 2025-07-08 372 .of_match_table = rt2880_wmac_match,
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 373 },
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 374 .probe = rt2800soc_probe,
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 375 .remove = rt2x00soc_remove,
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 @376 .suspend = rt2x00soc_suspend,
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 @377 .resume = rt2x00soc_resume,
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 378 };
fe7ef7c60c33fd drivers/net/wireless/rt2x00/rt2800soc.c Gabor Juhos 2013-10-17 379
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-09 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 20:17 [PATCHv2 wireless-next 0/7] wifi: rt2x00: add OF bindings + cleanup Rosen Penev
2025-07-08 20:17 ` [PATCHv2 wireless-next 1/7] wifi: rt2x00: add COMPILE_TEST Rosen Penev
2025-07-08 20:17 ` [PATCHv2 wireless-next 2/7] wifi: rt2x00: remove mod_name from platform_driver Rosen Penev
2025-07-08 20:17 ` [PATCHv2 wireless-next 3/7] wifi: rt2800soc: allow loading from OF Rosen Penev
2025-07-08 20:17 ` [PATCHv2 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc Rosen Penev
2025-07-09 9:30 ` kernel test robot [this message]
2025-07-08 20:17 ` [PATCHv2 wireless-next 5/7] wifi: rt2x00: soc: modernize probe Rosen Penev
2025-07-09 15:34 ` kernel test robot
2025-07-08 20:17 ` [PATCHv2 wireless-next 6/7] MIPS: dts: ralink: mt7620a: add wifi Rosen Penev
2025-07-08 20:17 ` [PATCHv2 wireless-next 7/7] dt-bindings: net: wireless: rt2800: add Rosen Penev
2025-07-08 21:28 ` Rob Herring (Arm)
2025-07-08 23:53 ` Rosen Penev
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=202507091735.YeYeU2tw-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=stf_xl@wp.pl \
--cc=tsbogend@alpha.franken.de \
/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).