From: kernel test robot <lkp@intel.com>
To: Matheus Giarola <matheustpgiarola@gmail.com>,
lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, matheusgiarola@usp.br,
arthurpilone@usp.br, davidbtadokoro@ime.usp.br
Subject: Re: [PATCH] iio: adc: ad7280a: replace mutex_lock() with guard(mutex)
Date: Sat, 21 Mar 2026 03:53:51 +0800 [thread overview]
Message-ID: <202603210357.KTWqlL36-lkp@intel.com> (raw)
In-Reply-To: <20260319184615.10970-1-matheusgiarola@usp.br>
Hi Matheus,
kernel test robot noticed the following build errors:
[auto build test ERROR on jic23-iio/togreg]
[also build test ERROR on linus/master v7.0-rc4 next-20260320]
[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/Matheus-Giarola/iio-adc-ad7280a-replace-mutex_lock-with-guard-mutex/20260320-142509
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20260319184615.10970-1-matheusgiarola%40usp.br
patch subject: [PATCH] iio: adc: ad7280a: replace mutex_lock() with guard(mutex)
config: parisc-randconfig-002-20260321 (https://download.01.org/0day-ci/archive/20260321/202603210357.KTWqlL36-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260321/202603210357.KTWqlL36-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/202603210357.KTWqlL36-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/iio/adc/ad7280a.c:10:
drivers/iio/adc/ad7280a.c: In function 'ad7280_read_raw':
>> include/linux/cleanup.h:299:2: error: a label can only be part of a statement and a declaration is not a statement
299 | class_##_name##_t var __cleanup(class_##_name##_destructor) = \
| ^~~~~~
include/linux/cleanup.h:419:2: note: in expansion of macro 'CLASS'
419 | CLASS(_name, __UNIQUE_ID(guard))
| ^~~~~
drivers/iio/adc/ad7280a.c:878:3: note: in expansion of macro 'guard'
878 | guard(mutex)(&st->lock);
| ^~~~~
--
In file included from ad7280a.c:10:
ad7280a.c: In function 'ad7280_read_raw':
>> include/linux/cleanup.h:299:2: error: a label can only be part of a statement and a declaration is not a statement
299 | class_##_name##_t var __cleanup(class_##_name##_destructor) = \
| ^~~~~~
include/linux/cleanup.h:419:2: note: in expansion of macro 'CLASS'
419 | CLASS(_name, __UNIQUE_ID(guard))
| ^~~~~
ad7280a.c:878:3: note: in expansion of macro 'guard'
878 | guard(mutex)(&st->lock);
| ^~~~~
vim +299 include/linux/cleanup.h
54da6a0924311c Peter Zijlstra 2023-05-26 297
54da6a0924311c Peter Zijlstra 2023-05-26 298 #define CLASS(_name, var) \
54da6a0924311c Peter Zijlstra 2023-05-26 @299 class_##_name##_t var __cleanup(class_##_name##_destructor) = \
54da6a0924311c Peter Zijlstra 2023-05-26 300 class_##_name##_constructor
54da6a0924311c Peter Zijlstra 2023-05-26 301
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-20 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:46 [PATCH] iio: adc: ad7280a: replace mutex_lock() with guard(mutex) Matheus Giarola
2026-03-20 19:53 ` kernel test robot [this message]
2026-03-20 20:16 ` kernel test robot
2026-03-21 15:55 ` Jonathan Cameron
2026-03-25 19:21 ` Matheus Giarola
2026-03-25 20:32 ` Jonathan Cameron
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=202603210357.KTWqlL36-lkp@intel.com \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=arthurpilone@usp.br \
--cc=davidbtadokoro@ime.usp.br \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matheusgiarola@usp.br \
--cc=matheustpgiarola@gmail.com \
--cc=nuno.sa@analog.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.