From: kernel test robot <lkp@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH][TEST-REQUEST] ASoC: makes CPU/Codec channel connection map more generic
Date: Thu, 19 Oct 2023 11:34:13 +0800 [thread overview]
Message-ID: <202310191138.KdPUHUfP-lkp@intel.com> (raw)
In-Reply-To: <87wmvjpdut.wl-kuninori.morimoto.gx@renesas.com>
Hi Kuninori,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-sound/for-next]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/UPDATE-20231019-100635/Kuninori-Morimoto/ASoC-makes-CPU-Codec-channel-connection-map-more-generic/20231017-140005
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/87wmvjpdut.wl-kuninori.morimoto.gx%40renesas.com
patch subject: [PATCH][TEST-REQUEST] ASoC: makes CPU/Codec channel connection map more generic
reproduce: (https://download.01.org/0day-ci/archive/20231019/202310191138.KdPUHUfP-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/202310191138.KdPUHUfP-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:SPLIT_STRING: quoted string split across lines
#248: FILE: sound/soc/soc-core.c:1087:
+ "dai_link->ch_maps[%d].connected_node (= %d) is "
+ "larger than max (= %d)",
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-19 3:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 1:37 [PATCH v4 0/4] ASoC: makes CPU/Codec channel connection map more generic Kuninori Morimoto
2023-10-16 1:37 ` [PATCH v4 1/4] " Kuninori Morimoto
2023-10-17 14:45 ` Pierre-Louis Bossart
2023-10-17 23:03 ` Kuninori Morimoto
2023-10-17 23:16 ` Pierre-Louis Bossart
2023-10-18 0:08 ` Kuninori Morimoto
2023-10-19 2:02 ` Kuninori Morimoto
2023-10-19 2:04 ` [PATCH][TEST-REQUEST] " Kuninori Morimoto
2023-10-19 3:34 ` kernel test robot [this message]
2023-10-19 15:32 ` Pierre-Louis Bossart
2023-10-19 23:55 ` Kuninori Morimoto
2023-10-16 1:37 ` [PATCH v4 2/4] ASoC: audio-graph-card2: add CPU:Codec = N:M support Kuninori Morimoto
2023-10-16 1:37 ` [PATCH v4 3/4] ASoC: audio-graph-card2-custom-sample: add CPU/Codec = N:M sample Kuninori Morimoto
2023-10-16 1:37 ` [PATCH v4 4/4] dt-bindings: audio-graph-port: add ch-maps property Kuninori Morimoto
2023-10-17 10:07 ` Conor Dooley
2023-10-16 8:25 ` [PATCH v4 0/4] ASoC: makes CPU/Codec channel connection map more generic Jerome Brunet
2023-10-16 22:59 ` Kuninori Morimoto
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=202310191138.KdPUHUfP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuninori.morimoto.gx@renesas.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.