From: kernel test robot <lkp@intel.com>
To: Mark Cilissen <mark@yotsuba.nl>
Cc: kbuild-all@lists.01.org, linux-acpi@vger.kernel.org,
devel@acpica.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Hans de Goede <hdegoede@redhat.com>
Subject: [rafael-pm:bleeding-edge 113/118] include/linux/mod_devicetable.h:587:25: warning: excess elements in array initializer
Date: Wed, 2 Mar 2022 10:51:10 +0800 [thread overview]
Message-ID: <202203020750.Uq6hGay2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head: f7307721a01f4f14d21c699b270a870370cf34b9
commit: ed00b2b8d737f87a2437d7bd7c7f90124b50da05 [113/118] x86 / ACPI: Work around broken XSDT on SEGA AALE board
config: i386-randconfig-a003 (https://download.01.org/0day-ci/archive/20220302/202203020750.Uq6hGay2-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=ed00b2b8d737f87a2437d7bd7c7f90124b50da05
git remote add rafael-pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
git fetch --no-tags rafael-pm bleeding-edge
git checkout ed00b2b8d737f87a2437d7bd7c7f90124b50da05
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/kernel/acpi/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/of.h:18,
from include/linux/irqdomain.h:35,
from include/linux/acpi.h:13,
from arch/x86/kernel/acpi/boot.c:11:
>> include/linux/mod_devicetable.h:587:25: warning: excess elements in array initializer
587 | #define DMI_MATCH(a, b) { .slot = a, .substr = b }
| ^
arch/x86/kernel/acpi/boot.c:1476:8: note: in expansion of macro 'DMI_MATCH'
1476 | DMI_MATCH(DMI_BIOS_DATE, "02/01/2011"),
| ^~~~~~~~~
include/linux/mod_devicetable.h:587:25: note: (near initialization for 'acpi_dmi_table[6].matches')
587 | #define DMI_MATCH(a, b) { .slot = a, .substr = b }
| ^
arch/x86/kernel/acpi/boot.c:1476:8: note: in expansion of macro 'DMI_MATCH'
1476 | DMI_MATCH(DMI_BIOS_DATE, "02/01/2011"),
| ^~~~~~~~~
vim +587 include/linux/mod_devicetable.h
d945b697d0eea5 David Woodhouse 2008-09-16 586
5017b2851373ee Jani Nikula 2013-07-03 @587 #define DMI_MATCH(a, b) { .slot = a, .substr = b }
5017b2851373ee Jani Nikula 2013-07-03 588 #define DMI_EXACT_MATCH(a, b) { .slot = a, .substr = b, .exact_match = 1 }
d2653e92732bd3 Jean Delvare 2008-04-29 589
:::::: The code at line 587 was first introduced by commit
:::::: 5017b2851373ee15c7035151853bb1448800cae2 dmi: add support for exact DMI matches in addition to substring matching
:::::: TO: Jani Nikula <jani.nikula@intel.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-02 2:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202203020750.Uq6hGay2-lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark@yotsuba.nl \
--cc=rjw@rjwysocki.net \
/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).