linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Luke D. Jones" <luke@ljones.dev>
Cc: oe-kbuild-all@lists.linux.dev, linux-input@vger.kernel.org,
	Jiri Kosina <jikos@kernel.org>
Subject: [hid:for-next 1/2] include/linux/platform_data/x86/asus-wmi.h:174:64: warning: missing braces around initializer
Date: Thu, 20 Jun 2024 16:37:46 +0800	[thread overview]
Message-ID: <202406201647.E2BChvPJ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-next
head:   fa9057ccb9c323816e0f2599a2d91f5c856b0004
commit: bda38f9a41d89b47dce54932f88d0e0edee00cae [1/2] HID: asus: use hid for brightness control on keyboard
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20240620/202406201647.E2BChvPJ-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240620/202406201647.E2BChvPJ-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/202406201647.E2BChvPJ-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/hid/hid-asus.c:29:
>> include/linux/platform_data/x86/asus-wmi.h:174:64: warning: missing braces around initializer [-Wmissing-braces]
     174 | static const struct dmi_system_id asus_use_hid_led_dmi_ids[] = {
         |                                                                ^


vim +174 include/linux/platform_data/x86/asus-wmi.h

   173	
 > 174	static const struct dmi_system_id asus_use_hid_led_dmi_ids[] = {
   175		{
   176			.matches = {
   177				DMI_MATCH(DMI_PRODUCT_FAMILY, "ROG Zephyrus"),
   178			},
   179		},
   180		{
   181			.matches = {
   182				DMI_MATCH(DMI_PRODUCT_FAMILY, "ROG Strix"),
   183			},
   184		},
   185		{
   186			.matches = {
   187				DMI_MATCH(DMI_PRODUCT_FAMILY, "ROG Flow"),
   188			},
   189		},
   190		{
   191			.matches = {
   192				DMI_MATCH(DMI_BOARD_NAME, "GA403"),
   193			},
   194		},
   195		{
   196			.matches = {
   197				DMI_MATCH(DMI_BOARD_NAME, "GU605"),
   198			},
   199		},
   200		{
   201			.matches = {
   202				DMI_MATCH(DMI_BOARD_NAME, "RC71L"),
   203			},
   204		},
   205		NULL,
   206	};
   207	

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

                 reply	other threads:[~2024-06-20  8:38 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=202406201647.E2BChvPJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).