From: kernel test robot <lkp@intel.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
jic23@kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Antoniu Miclaus <antoniu.miclaus@analog.com>
Subject: Re: [PATCH v4 2/2] iio: amplifiers: adl8113: add driver support
Date: Sat, 29 Nov 2025 02:46:07 +0800 [thread overview]
Message-ID: <202511290251.tcqKd4O5-lkp@intel.com> (raw)
In-Reply-To: <20251121095204.18574-3-antoniu.miclaus@analog.com>
Hi Antoniu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on robh/for-next linus/master v6.18-rc7 next-20251128]
[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/Antoniu-Miclaus/dt-bindings-iio-amplifiers-add-adl8113/20251121-180600
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20251121095204.18574-3-antoniu.miclaus%40analog.com
patch subject: [PATCH v4 2/2] iio: amplifiers: adl8113: add driver support
config: x86_64-randconfig-r071-20251128 (https://download.01.org/0day-ci/archive/20251129/202511290251.tcqKd4O5-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
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/202511290251.tcqKd4O5-lkp@intel.com/
smatch warnings:
drivers/iio/amplifiers/adl8113.c:58 adl8113_set_path() warn: inconsistent indenting
vim +58 drivers/iio/amplifiers/adl8113.c
48
49 static int adl8113_set_path(struct adl8113_state *st,
50 enum adl8113_signal_path path)
51 {
52 int va, vb;
53
54 /* Determine GPIO values based on signal path */
55 switch (path) {
56 case ADL8113_INTERNAL_AMP:
57 va = 0; vb = 0; /* Internal amplifier */
> 58 break;
59 case ADL8113_INTERNAL_BYPASS:
60 va = 1; vb = 1; /* Internal bypass */
61 break;
62 case ADL8113_EXTERNAL_A:
63 va = 0; vb = 1; /* External bypass A */
64 break;
65 case ADL8113_EXTERNAL_B:
66 va = 1; vb = 0; /* External bypass B */
67 break;
68 default:
69 return -EINVAL;
70 }
71
72 gpiod_set_value(st->gpio_va, va);
73 gpiod_set_value(st->gpio_vb, vb);
74 st->current_path = path;
75 return 0;
76 }
77
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-11-28 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 9:52 [PATCH v4 0/2] iio: amplifiers: add support for ADL8113 Low Noise Amplifier Antoniu Miclaus
2025-11-21 9:52 ` [PATCH v4 1/2] dt-bindings: iio: amplifiers: add adl8113 Antoniu Miclaus
2025-11-22 16:17 ` David Lechner
2025-11-21 9:52 ` [PATCH v4 2/2] iio: amplifiers: adl8113: add driver support Antoniu Miclaus
2025-11-22 16:52 ` David Lechner
2025-11-28 18:46 ` kernel test robot [this message]
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=202511290251.tcqKd4O5-lkp@intel.com \
--to=lkp@intel.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®