From: kernel test robot <lkp@intel.com>
To: Ivan Orlov <ivan.orlov0322@gmail.com>, <perex@perex.cz>,
<tiwai@suse.com>, <corbet@lwn.net>, <broonie@kernel.org>,
<shuah@kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>,
Ivan Orlov <ivan.orlov0322@gmail.com>,
<linux-kselftest@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<aholzinger@gmx.de>
Subject: Re: [PATCH 4/4] selftests: ALSA: Cover userspace-driven timers with test
Date: Sun, 28 Jul 2024 14:10:07 +0800 [thread overview]
Message-ID: <ZqXgv8QyRabQ31ig@rli9-mobl> (raw)
In-Reply-To: <20240726074750.626671-5-ivan.orlov0322@gmail.com>
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tiwai-sound/for-next]
[also build test WARNING on tiwai-sound/for-linus linus/master v6.10 next-20240726]
[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/Ivan-Orlov/ALSA-aloop-Allow-using-global-timers/20240726-155158
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
patch link: https://lore.kernel.org/r/20240726074750.626671-5-ivan.orlov0322%40gmail.com
patch subject: [PATCH 4/4] selftests: ALSA: Cover userspace-driven timers with test
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240728/202407281359.vMYdESrT-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/r/202407281359.vMYdESrT-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> utimer-test.c:73:1: warning: non-void function does not return a value [-Wreturn-type]
73 | }
| ^
>> utimer-test.c:117:11: warning: enumeration value 'TIMER_NO_EVENT' not handled in switch [-Wswitch]
117 | switch (parse_timer_output(buf)) {
| ^~~~~~~~~~~~~~~~~~~~~~~
2 warnings generated.
vim +73 tools/testing/selftests/alsa/utimer-test.c
5cf58530fa628b Ivan Orlov 2024-07-26 62
5cf58530fa628b Ivan Orlov 2024-07-26 63 static void *ticking_func(void *data)
5cf58530fa628b Ivan Orlov 2024-07-26 64 {
5cf58530fa628b Ivan Orlov 2024-07-26 65 int i;
5cf58530fa628b Ivan Orlov 2024-07-26 66 int *fd = (int *)data;
5cf58530fa628b Ivan Orlov 2024-07-26 67
5cf58530fa628b Ivan Orlov 2024-07-26 68 for (i = 0; i < TICKS_COUNT; i++) {
5cf58530fa628b Ivan Orlov 2024-07-26 69 /* Well, trigger the timer! */
5cf58530fa628b Ivan Orlov 2024-07-26 70 ioctl(*fd, SNDRV_TIMER_IOCTL_TRIGGER, NULL);
5cf58530fa628b Ivan Orlov 2024-07-26 71 sleep(TIMER_FREQ_SEC);
5cf58530fa628b Ivan Orlov 2024-07-26 72 }
5cf58530fa628b Ivan Orlov 2024-07-26 @73 }
5cf58530fa628b Ivan Orlov 2024-07-26 74
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-28 6:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:47 [PATCH 0/4] Introduce userspace-driven ALSA timers Ivan Orlov
2024-07-26 7:47 ` [PATCH 1/4] ALSA: aloop: Allow using global timers Ivan Orlov
2024-07-26 7:47 ` [PATCH 2/4] Docs/sound: Add documentation for userspace-driven ALSA timers Ivan Orlov
2024-07-26 7:47 ` [PATCH 3/4] ALSA: timer: Introduce virtual userspace-driven timers Ivan Orlov
2024-07-28 6:52 ` Christophe JAILLET
2024-07-28 8:49 ` Ivan Orlov
2024-07-28 6:59 ` Christophe JAILLET
2024-07-28 8:51 ` Ivan Orlov
2024-07-28 9:30 ` Christophe JAILLET
2024-07-28 9:42 ` Ivan Orlov
2024-07-28 10:29 ` Christophe JAILLET
2024-07-28 11:54 ` Ivan Orlov
2024-07-26 7:47 ` [PATCH 4/4] selftests: ALSA: Cover userspace-driven timers with test Ivan Orlov
2024-07-28 6:10 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-28 5:40 kernel test robot
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=ZqXgv8QyRabQ31ig@rli9-mobl \
--to=lkp@intel.com \
--cc=aholzinger@gmx.de \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=perex@perex.cz \
--cc=shuah@kernel.org \
--cc=tiwai@suse.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.