From: kernel test robot <lkp@intel.com>
To: "marcelo.schmitt@analog.com" <marcelo.schmitt@analog.com>,
beniamin.bia@analog.com, paul.cercueil@analog.com,
Michael.Hennerich@analog.com, lars@metafoo.de, jic23@kernel.org,
marcelo.schmitt1@gmail.com
Cc: oe-kbuild-all@lists.linux.dev,
Marcelo Schmitt <marcelo.schmitt@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] iio: adc: ad7091r: Move defines to header file
Date: Wed, 22 Nov 2023 20:40:50 +0800 [thread overview]
Message-ID: <202311221730.lHHfx8Ft-lkp@intel.com> (raw)
In-Reply-To: <8aa859817e86408733a81cf31b932f0efa273c71.1700595310.git.marcelo.schmitt1@gmail.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.7-rc2 next-20231122]
[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/marcelo-schmitt-analog-com/MAINTAINERS-Add-MAINTAINERS-entry-for-AD7091R/20231122-093706
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/8aa859817e86408733a81cf31b932f0efa273c71.1700595310.git.marcelo.schmitt1%40gmail.com
patch subject: [PATCH 3/7] iio: adc: ad7091r: Move defines to header file
config: powerpc-randconfig-r071-20231122 (https://download.01.org/0day-ci/archive/20231122/202311221730.lHHfx8Ft-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231122/202311221730.lHHfx8Ft-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/202311221730.lHHfx8Ft-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/iio/adc/ad7091r-base.c:16:
>> drivers/iio/adc/ad7091r-base.h:41:36: warning: 'ad7091r_events' defined but not used [-Wunused-const-variable=]
41 | static const struct iio_event_spec ad7091r_events[] = {
| ^~~~~~~~~~~~~~
vim +/ad7091r_events +41 drivers/iio/adc/ad7091r-base.h
40
> 41 static const struct iio_event_spec ad7091r_events[] = {
42 {
43 .type = IIO_EV_TYPE_THRESH,
44 .dir = IIO_EV_DIR_RISING,
45 .mask_separate = BIT(IIO_EV_INFO_VALUE) |
46 BIT(IIO_EV_INFO_ENABLE),
47 },
48 {
49 .type = IIO_EV_TYPE_THRESH,
50 .dir = IIO_EV_DIR_FALLING,
51 .mask_separate = BIT(IIO_EV_INFO_VALUE) |
52 BIT(IIO_EV_INFO_ENABLE),
53 },
54 {
55 .type = IIO_EV_TYPE_THRESH,
56 .dir = IIO_EV_DIR_EITHER,
57 .mask_separate = BIT(IIO_EV_INFO_HYSTERESIS),
58 },
59 };
60
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-22 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 21:33 [PATCH 0/7] Add support for AD7091R-2/-4/-8 marcelo.schmitt
2023-11-21 21:34 ` [PATCH 1/7] iio: adc: ad7091r-base: Set alert config and drvdata marcelo.schmitt
2023-11-21 21:35 ` [PATCH 2/7] MAINTAINERS: Add MAINTAINERS entry for AD7091R marcelo.schmitt
2023-11-21 21:35 ` [PATCH 3/7] iio: adc: ad7091r: Move defines to header file marcelo.schmitt
2023-11-22 12:40 ` kernel test robot [this message]
2023-11-21 21:35 ` [PATCH 4/7] iio: adc: ad7091r: Alloc IIO device before generic probe marcelo.schmitt
2023-11-21 21:36 ` [PATCH 5/7] dt-bindings: iio: Add binding documentation for AD7091R-8 marcelo.schmitt
2023-11-22 9:57 ` Krzysztof Kozlowski
2023-11-22 12:40 ` kernel test robot
2023-11-21 21:36 ` [PATCH 6/7] iio: adc: Add support " marcelo.schmitt
2023-11-22 10:01 ` Krzysztof Kozlowski
2023-11-23 6:30 ` Dan Carpenter
2023-11-21 21:36 ` [PATCH 7/7] iio: adc: ad7091r-base: Add debugfs reg access marcelo.schmitt
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=202311221730.lHHfx8Ft-lkp@intel.com \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=beniamin.bia@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul.cercueil@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).