From: kernel test robot <lkp@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [plbossart-sound:sdw/sdca-function-devices 25/26] sound/soc/sdca/sdca_function_uaj.c:37:19: warning: initializer-string for array of 'char' is too long
Date: Wed, 22 May 2024 20:07:15 +0800 [thread overview]
Message-ID: <202405222043.WIb43U9B-lkp@intel.com> (raw)
tree: https://github.com/plbossart/sound sdw/sdca-function-devices
head: f46b8e859911a824897639b737e4df43e17e1f42
commit: 2ac8e1bbf1ec8eeb41f02e27879939321999656b [25/26] ASoC: SDCA: add function devices
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20240522/202405222043.WIb43U9B-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240522/202405222043.WIb43U9B-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/202405222043.WIb43U9B-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/sdca/sdca_function_uaj.c:37:19: warning: initializer-string for array of 'char' is too long
37 | { .name = "snd_soc_sdca.SDCA_FUNCTION_TYPE_UAJ_NAME" },
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sound/soc/sdca/sdca_function_uaj.c:37:19: note: (near initialization for 'sdca_uaj_id_table[0].name')
vim +/char +37 sound/soc/sdca/sdca_function_uaj.c
35
36 static const struct auxiliary_device_id sdca_uaj_id_table[] = {
> 37 { .name = "snd_soc_sdca.SDCA_FUNCTION_TYPE_UAJ_NAME" },
38 {},
39 };
40 MODULE_DEVICE_TABLE(auxiliary, sdca_uaj_id_table);
41
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-22 12:08 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=202405222043.WIb43U9B-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pierre-louis.bossart@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.