[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <201801250253.o4jdYyJW%fengguang.wu@intel.com>
Date: Thu, 25 Jan 2018 02:53:42 +0800
From: kbuild test robot <lkp@...el.com>
To: Shreeya Patel <shreeya.patel23498@...il.com>
Cc: kbuild-all@...org, lars@...afoo.de, Michael.Hennerich@...log.com,
jic23@...nel.org, knaack.h@....de, pmeerw@...erw.net,
gregkh@...uxfoundation.org, linux-iio@...r.kernel.org,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
Shreeya Patel <shreeya.patel23498@...il.com>
Subject: Re: [PATCH] Staging: iio: ade7758: Expand buf_lock to cover both
buffer
Hi Shreeya,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.15-rc9 next-20180119]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Shreeya-Patel/Staging-iio-ade7758-Expand-buf_lock-to-cover-both-buffer/20180124-234049
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/staging/iio/meter/ade7758_core.c:28:5: sparse: symbol '__ade7758_spi_write_reg_8' was not declared. Should it be
>> drivers/staging/iio/meter/ade7758_core.c:104:5: sparse: symbol '__ade7758_spi_read_reg_8' was not declared. Should it be
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists