From: kernel test robot <lkp@intel.com>
To: Gergo Koteles <soyer@irl.hu>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Takashi Iwai <tiwai@suse.de>
Subject: [linux-next:master 11897/12662] sound/pci/hda/tas2781_hda_i2c.c:433:30: sparse: sparse: incorrect type in assignment (different base types)
Date: Sun, 7 Jan 2024 22:11:11 +0800 [thread overview]
Message-ID: <202401072137.Oc7pQgRW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e2425464bc87159274879ab30f9d4fe624b9fcd2
commit: c3ca4458cc2f719b1652abaa8d2fbf7f3d4311cb [11897/12662] ALSA: hda/tas2781: add TAS2563 support for 14ARB7
config: x86_64-randconfig-122-20240107 (https://download.01.org/0day-ci/archive/20240107/202401072137.Oc7pQgRW-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240107/202401072137.Oc7pQgRW-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/202401072137.Oc7pQgRW-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> sound/pci/hda/tas2781_hda_i2c.c:433:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int data @@ got restricted __be32 [usertype] @@
sound/pci/hda/tas2781_hda_i2c.c:433:30: sparse: expected unsigned int data
sound/pci/hda/tas2781_hda_i2c.c:433:30: sparse: got restricted __be32 [usertype]
vim +433 sound/pci/hda/tas2781_hda_i2c.c
424
425 static void tas2563_apply_calib(struct tasdevice_priv *tas_priv)
426 {
427 unsigned int data;
428 int offset = 0;
429 int ret;
430
431 for (int i = 0; i < tas_priv->ndev; i++) {
432 for (int j = 0; j < TAS2563_CAL_N; ++j) {
> 433 data = cpu_to_be32(
434 *(uint32_t *)&tas_priv->cali_data.data[offset]);
435 ret = tasdevice_dev_bulk_write(tas_priv, i, cal_regs[j],
436 (unsigned char *)&data, TAS2563_CAL_DATA_SIZE);
437 if (ret)
438 dev_err(tas_priv->dev,
439 "Error writing calib regs\n");
440 offset += TAS2563_CAL_DATA_SIZE;
441 }
442 }
443 }
444
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-07 14:11 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=202401072137.Oc7pQgRW-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=soyer@irl.hu \
--cc=tiwai@suse.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