From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: include/linux/iio/iio.h:781 class___priv__iio_dev_mode_lock_try_direct_constructor() warn: passing zero to 'ERR_PTR'
Date: Sat, 11 Jul 2026 20:38:37 +0800 [thread overview]
Message-ID: <202607111940.WTcT5zEX-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Radu Sabau <radu.sabau@analog.com>
CC: Jonathan Cameron <jic23@kernel.org>
CC: David Lechner <dlechner@baylibre.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dd3210c47e8d3ac6b4e9141fc68acc03b38c0ba3
commit: 40850443aa1239f71fc65b870a0f0ecd54e42c9d iio: adc: ad4691: add initial driver for AD4691 family
date: 6 weeks ago
:::::: branch date: 10 hours ago
:::::: commit date: 6 weeks ago
config: x86_64-randconfig-161-20260708 (https://download.01.org/0day-ci/archive/20260711/202607111940.WTcT5zEX-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9185-gbcc58b9c
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
| Fixes: 40850443aa12 ("iio: adc: ad4691: add initial driver for AD4691 family")
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202607111940.WTcT5zEX-lkp@intel.com/
smatch warnings:
include/linux/iio/iio.h:781 class___priv__iio_dev_mode_lock_try_direct_constructor() warn: passing zero to 'ERR_PTR'
vim +/ERR_PTR +781 include/linux/iio/iio.h
847ec80bbaa76a drivers/staging/iio/iio.h Jonathan Cameron 2009-08-18 772
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 773 /*
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 774 * These classes are not meant to be used directly by drivers (hence the
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 775 * __priv__ prefix). Instead, documented wrapper macros are provided below to
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 776 * enforce the use of ACQUIRE() or guard() semantics and avoid the problematic
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 777 * scoped guard variants.
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 778 */
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 779 DEFINE_GUARD(__priv__iio_dev_mode_lock, struct iio_dev *,
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 780 __iio_dev_mode_lock(_T), __iio_dev_mode_unlock(_T));
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 @781 DEFINE_GUARD_COND(__priv__iio_dev_mode_lock, _try_direct,
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 782 iio_device_claim_direct(_T));
7a38b75da1dc38 include/linux/iio/iio.h Kurt Borja 2026-01-20 783
:::::: The code at line 781 was first introduced by commit
:::::: 7a38b75da1dc38a8cd9563c41b87367b2475b975 iio: core: Add cleanup.h support for iio_device_claim_*()
:::::: TO: Kurt Borja <kuurtb@gmail.com>
:::::: CC: Jonathan Cameron <Jonathan.Cameron@huawei.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-11 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607111940.WTcT5zEX-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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.