Linux-MIPS Archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-mips@vger.kernel.org,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: [mips-linux:mips-next 47/56] arch/mips/ralink/timer.c:136:48: error: array has incomplete element type 'const struct of_device_id'
Date: Tue, 12 Mar 2024 09:38:38 +0800	[thread overview]
Message-ID: <202403120926.hoXbeGnb-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git mips-next
head:   732932220078f6312f3ef57c17523d3d7f995655
commit: 5804be0618486f8979208e323188e44f8013a6a3 [47/56] MIPS: ralink: Remove unused of_gpio.h
config: mips-rt305x_defconfig (https://download.01.org/0day-ci/archive/20240312/202403120926.hoXbeGnb-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 503c55e17037436dcd45ac69dea8967e67e3f5e8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240312/202403120926.hoXbeGnb-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/202403120926.hoXbeGnb-lkp@intel.com/

Note: the mips-linux/mips-next HEAD 732932220078f6312f3ef57c17523d3d7f995655 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

>> arch/mips/ralink/timer.c:136:48: error: array has incomplete element type 'const struct of_device_id'
     136 | static const struct of_device_id rt_timer_match[] = {
         |                                                ^
   include/linux/device/driver.h:106:15: note: forward declaration of 'struct of_device_id'
     106 |         const struct of_device_id       *of_match_table;
         |                      ^
   1 error generated.


vim +136 arch/mips/ralink/timer.c

80ecbd245791fe John Crispin 2013-08-08  135  
80ecbd245791fe John Crispin 2013-08-08 @136  static const struct of_device_id rt_timer_match[] = {
80ecbd245791fe John Crispin 2013-08-08  137  	{ .compatible = "ralink,rt2880-timer" },
80ecbd245791fe John Crispin 2013-08-08  138  	{},
80ecbd245791fe John Crispin 2013-08-08  139  };
80ecbd245791fe John Crispin 2013-08-08  140  

:::::: The code at line 136 was first introduced by commit
:::::: 80ecbd245791fec5da4baa88c7273ec7f9ae7782 MIPS: ralink: Add support for periodic timer irq

:::::: TO: John Crispin <blogic@openwrt.org>
:::::: CC: Ralf Baechle <ralf@linux-mips.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-03-12  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  1:38 kernel test robot [this message]
2024-03-12 14:34 ` [mips-linux:mips-next 47/56] arch/mips/ralink/timer.c:136:48: error: array has incomplete element type 'const struct of_device_id' Andy Shevchenko

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=202403120926.hoXbeGnb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).