From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@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: Re: [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 16:34:48 +0200 [thread overview]
Message-ID: <ZfBoCBta1cnguCww@smile.fi.intel.com> (raw)
In-Reply-To: <202403120926.hoXbeGnb-lkp@intel.com>
On Tue, Mar 12, 2024 at 09:38:38AM +0800, kernel test robot wrote:
> 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/
Fix already had been sent and applied.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-03-12 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 1:38 [mips-linux:mips-next 47/56] arch/mips/ralink/timer.c:136:48: error: array has incomplete element type 'const struct of_device_id' kernel test robot
2024-03-12 14:34 ` Andy Shevchenko [this message]
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=ZfBoCBta1cnguCww@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--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