From: kernel test robot <lkp@intel.com>
To: Jyri Sarha <jyri.sarha@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jsarha:set_multi_pipeline_state_debug 1/1] sound/soc/sof/ipc4-pcm.c:66:10: warning: use of unary operator that may be intended as compound assignment (+=)
Date: Thu, 20 Mar 2025 05:05:07 +0800 [thread overview]
Message-ID: <202503200412.DFJ8fDi2-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux set_multi_pipeline_state_debug
head: 70b57c25bce492b37b15b2c8242f3af34b9fda2c
commit: 70b57c25bce492b37b15b2c8242f3af34b9fda2c [1/1] ASoC: SOF: ipc4-pcm: Pipe instances to dev_dbg in multi_pipeline_state()
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20250320/202503200412.DFJ8fDi2-lkp@intel.com/config)
compiler: clang version 20.1.0 (https://github.com/llvm/llvm-project 24a30daaa559829ad079f2ff7f73eb4e18095f88)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250320/202503200412.DFJ8fDi2-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/202503200412.DFJ8fDi2-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/sof/ipc4-pcm.c:66:10: warning: use of unary operator that may be intended as compound assignment (+=)
66 | offset =+ snprintf(buf + offset, size - offset, " %d",
| ^~
1 warning generated.
vim +66 sound/soc/sof/ipc4-pcm.c
58
59 static
60 char *sof_ipc4_set_multi_pipeline_state_debug(struct snd_sof_dev *sdev, char *buf, size_t size,
61 struct ipc4_pipeline_set_state_data *trigger_list)
62 {
63 int i, offset = 0;
64
65 for (i = 0; i < trigger_list->count; i++) {
> 66 offset =+ snprintf(buf + offset, size - offset, " %d",
67 trigger_list->pipeline_instance_ids[i]);
68
69 if (offset >= size - 1) {
70 buf[size - 1] = '\0';
71 break;
72 }
73 }
74 return buf;
75 }
76
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-19 21:06 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=202503200412.DFJ8fDi2-lkp@intel.com \
--to=lkp@intel.com \
--cc=jyri.sarha@linux.intel.com \
--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 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.