From: kernel test robot <lkp@intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
alsa-devel@alsa-project.org, broonie@kernel.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
upstream@semihalf.com, harshapriya.n@intel.com, rad@semihalf.com,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
hdegoede@redhat.com, amadeuszx.slawinski@linux.intel.com,
kbuild-all@lists.01.org, cujomalainey@chromium.org,
lma@semihalf.com
Subject: Re: [PATCH v2 09/15] ASoC: Intel: avs: Event tracing
Date: Mon, 9 May 2022 22:42:12 +0800 [thread overview]
Message-ID: <202205092213.XXm7bdgE-lkp@intel.com> (raw)
In-Reply-To: <20220509085821.3852259-10-cezary.rojewski@intel.com>
Hi Cezary,
I love your patch! Yet something to improve:
[auto build test ERROR on broonie-sound/for-next]
[also build test ERROR on next-20220509]
[cannot apply to tiwai-sound/for-next v5.18-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Cezary-Rojewski/ASoC-Intel-avs-Driver-core-and-PCM-operations/20220509-165656
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20220509/202205092213.XXm7bdgE-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/22736f1a80f21a1729c0b0169ab6b7d724fab1d7
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Cezary-Rojewski/ASoC-Intel-avs-Driver-core-and-PCM-operations/20220509-165656
git checkout 22736f1a80f21a1729c0b0169ab6b7d724fab1d7
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=alpha SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> sound/soc/intel/avs/trace.c:19:6: error: redefinition of 'trace_avs_msg_payload'
19 | void trace_avs_msg_payload(const void *data, size_t size)
| ^~~~~~~~~~~~~~~~~~~~~
In file included from sound/soc/intel/avs/trace.c:12:
sound/soc/intel/avs/trace.h:41:20: note: previous definition of 'trace_avs_msg_payload' with type 'void(const void *, size_t)' {aka 'void(const void *, long unsigned int)'}
41 | static inline void trace_avs_msg_payload(const void *data, size_t size) {};
| ^~~~~~~~~~~~~~~~~~~~~
vim +/trace_avs_msg_payload +19 sound/soc/intel/avs/trace.c
13
14 #define BYTES_PER_LINE 16
15 #define MAX_CHUNK_SIZE ((PAGE_SIZE - 150) /* Place for trace header */ \
16 / (2 * BYTES_PER_LINE + 4) /* chars per line */ \
17 * BYTES_PER_LINE)
18
> 19 void trace_avs_msg_payload(const void *data, size_t size)
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-09 14:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 8:58 [PATCH v2 00/15] ASoC: Intel: avs: Driver core and PCM operations Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 01/15] ASoC: Intel: avs: Account for libraries when booting basefw Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 02/15] ASoC: Intel: avs: Generic soc component driver Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 03/15] ASoC: Intel: avs: Generic PCM FE operations Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 04/15] ASoC: Intel: avs: non-HDA PCM BE operations Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 05/15] ASoC: Intel: avs: HDA " Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 06/15] ASoC: Intel: avs: Coredump and recovery flow Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 07/15] ASoC: Intel: avs: Prepare for firmware tracing Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 08/15] ASoC: Intel: avs: D0ix power state support Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 09/15] ASoC: Intel: avs: Event tracing Cezary Rojewski
2022-05-09 14:42 ` kernel test robot [this message]
2022-05-09 8:58 ` [PATCH v2 10/15] ASoC: Intel: avs: Replace link_mask usage with i2s_link_mask Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 11/15] ASoC: Intel: avs: Machine board registration Cezary Rojewski
2022-05-09 11:58 ` kernel test robot
2022-05-09 12:38 ` Amadeusz Sławiński
2022-05-14 2:49 ` Vineet Gupta
2022-05-14 2:49 ` Vineet Gupta
2022-05-14 13:20 ` Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 12/15] ASoC: Intel: avs: PCI driver implementation Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 13/15] ASoC: Intel: avs: Power management Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 14/15] ASoC: Intel: avs: SKL-based platforms support Cezary Rojewski
2022-05-09 8:58 ` [PATCH v2 15/15] ASoC: Intel: avs: APL-based " Cezary Rojewski
2022-05-17 17:21 ` [PATCH v2 00/15] ASoC: Intel: avs: Driver core and PCM operations Mark Brown
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=202205092213.XXm7bdgE-lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=cujomalainey@chromium.org \
--cc=harshapriya.n@intel.com \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=lma@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rad@semihalf.com \
--cc=tiwai@suse.com \
--cc=upstream@semihalf.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.