From: Jonathan Cameron <jic23@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
oe-kbuild-all@lists.linux.dev,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/7] iio: accel: kx022a: align with subsystem way
Date: Sat, 30 Nov 2024 18:08:44 +0000 [thread overview]
Message-ID: <20241130180844.27a5c8e0@jic23-huawei> (raw)
In-Reply-To: <202411290107.KXHPQXRf-lkp@intel.com>
On Fri, 29 Nov 2024 01:20:41 +0800
kernel test robot <lkp@intel.com> wrote:
> Hi Matti,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on a61ff7eac77e86de828fe28c4e42b8ae9ec2b195]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Matti-Vaittinen/iio-accel-kx022a-Use-cleanup-h-helpers/20241128-170626
> base: a61ff7eac77e86de828fe28c4e42b8ae9ec2b195
> patch link: https://lore.kernel.org/r/9b63813ecf10b1cd0126cb950bc09514c4287b9a.1732783834.git.mazziesaccount%40gmail.com
> patch subject: [PATCH v3 7/7] iio: accel: kx022a: align with subsystem way
> config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20241129/202411290107.KXHPQXRf-lkp@intel.com/config)
> compiler: loongarch64-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241129/202411290107.KXHPQXRf-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/202411290107.KXHPQXRf-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/iio/accel/kionix-kx022a.c: In function 'kx022a_write_raw':
> drivers/iio/accel/kionix-kx022a.c:507:9: error: implicit declaration of function 'if_not_cond_guard' [-Wimplicit-function-declaration]
> 507 | if_not_cond_guard(iio_claim_direct_try, idev)
> | ^~~~~~~~~~~~~~~~~
> drivers/iio/accel/kionix-kx022a.c:507:27: error: 'iio_claim_direct_try' undeclared (first use in this function); did you mean 'class_iio_claim_direct_try_t'?
> 507 | if_not_cond_guard(iio_claim_direct_try, idev)
> | ^~~~~~~~~~~~~~~~~~~~
> | class_iio_claim_direct_try_t
> drivers/iio/accel/kionix-kx022a.c:507:27: note: each undeclared identifier is reported only once for each function it appears in
> drivers/iio/accel/kionix-kx022a.c:507:54: error: expected ';' before 'return'
> 507 | if_not_cond_guard(iio_claim_direct_try, idev)
> | ^
> | ;
> 508 | return -EBUSY;
> | ~~~~~~
> In file included from drivers/iio/accel/kionix-kx022a.c:8:
> >> include/linux/cleanup.h:308:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
> 308 | for (CLASS(_name, scope)(args), \
> | ^~~
> drivers/iio/accel/kionix-kx022a.c:521:17: note: in expansion of macro 'scoped_guard'
> 521 | scoped_guard(mutex, &data->mutex) {
> | ^~~~~~~~~~~~
> drivers/iio/accel/kionix-kx022a.c:532:9: note: here
> 532 | case IIO_CHAN_INFO_SCALE:
> | ^~~~
>
The precursor is coming through tip as I understand it.
I'll have to hold off on applying this until after rc1.
>
> vim +308 include/linux/cleanup.h
>
> e4ab322fbaaaf8 Peter Zijlstra 2023-09-17 306
> 54da6a0924311c Peter Zijlstra 2023-05-26 307 #define scoped_guard(_name, args...) \
> 54da6a0924311c Peter Zijlstra 2023-05-26 @308 for (CLASS(_name, scope)(args), \
> e4ab322fbaaaf8 Peter Zijlstra 2023-09-17 309 *done = NULL; __guard_ptr(_name)(&scope) && !done; done = (void *)1)
> e4ab322fbaaaf8 Peter Zijlstra 2023-09-17 310
>
next prev parent reply other threads:[~2024-11-30 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 9:01 [PATCH v3 0/7] Support ROHM KX134ACR-LBZ Matti Vaittinen
2024-11-28 9:01 ` [PATCH v3 1/7] iio: accel: kx022a: Use cleanup.h helpers Matti Vaittinen
2024-11-30 18:05 ` Jonathan Cameron
2024-11-28 9:02 ` [PATCH v3 2/7] iio: accel: kx022a: Support ICs with different G-ranges Matti Vaittinen
2024-12-02 10:25 ` Mehdi Djait
2024-12-02 11:05 ` Matti Vaittinen
2024-11-28 9:02 ` [PATCH v3 3/7] dt-bindings: ROHM KX134ACR-LBZ Matti Vaittinen
2024-11-28 9:02 ` [PATCH v3 4/7] iio: kx022a: Support " Matti Vaittinen
2024-11-30 18:06 ` Jonathan Cameron
2024-11-28 9:03 ` [PATCH v3 5/7] dt-bindings: iio: kx022a: Support KX134-1211 Matti Vaittinen
2024-11-28 9:03 ` [PATCH v3 6/7] iio: accel: " Matti Vaittinen
2024-11-30 18:07 ` Jonathan Cameron
2024-11-28 9:03 ` [PATCH v3 7/7] iio: accel: kx022a: align with subsystem way Matti Vaittinen
2024-11-28 17:20 ` kernel test robot
2024-11-30 18:08 ` Jonathan Cameron [this message]
2024-11-28 17:31 ` kernel test robot
2024-11-28 17:52 ` kernel test robot
2024-11-30 18:15 ` Jonathan Cameron
2024-11-30 18:26 ` Jonathan Cameron
2024-12-02 6:46 ` Matti Vaittinen
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=20241130180844.27a5c8e0@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox