From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, <kbuild-all@lists.01.org>,
<linux-kernel@vger.kernel.org>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Mihail Chindris <mihail.chindris@analog.com>
Subject: Re: [jic23-iio:testing 149/151] drivers/iio/buffer/kfifo_buf.c:165:9: sparse: sparse: cast to restricted __poll_t
Date: Wed, 13 Oct 2021 18:40:01 +0100 [thread overview]
Message-ID: <20211013184001.00005b76@Huawei.com> (raw)
In-Reply-To: <202110110440.lDjKV8lX-lkp@intel.com>
On Mon, 11 Oct 2021 04:39:48 +0800
kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
> head: 687109cbbfd744cba8aea3580770dcf6e13ce12a
> commit: dc02c5452d3a3c2792efae0b6b436634915384ac [149/151] iio: kfifo-buffer: Add output buffer support
> config: xtensa-randconfig-s031-20211010 (attached as .config)
> compiler: xtensa-linux-gcc (GCC) 11.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?id=dc02c5452d3a3c2792efae0b6b436634915384ac
> git remote add jic23-iio https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> git fetch --no-tags jic23-iio testing
> git checkout dc02c5452d3a3c2792efae0b6b436634915384ac
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=xtensa SHELL=/bin/bash drivers/iio/buffer/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
> >> drivers/iio/buffer/kfifo_buf.c:165:9: sparse: sparse: cast to restricted __poll_t
>
> vim +165 drivers/iio/buffer/kfifo_buf.c
>
> 152
> 153 static int iio_kfifo_remove_from(struct iio_buffer *r, void *data)
> 154 {
> 155 int ret;
> 156 struct iio_kfifo *kf = iio_to_kfifo(r);
> 157
> 158 if (kfifo_size(&kf->kf) < 1)
> 159 return -EBUSY;
> 160
> 161 ret = kfifo_out(&kf->kf, data, 1);
> 162 if (ret != 1)
> 163 return -EBUSY;
> 164
> > 165 wake_up_interruptible_poll(&r->pollq, POLLOUT | POLLWRNORM);
These should be EPOLLOUT and EPOLLWRNORM I believe. I'll apply a fixup.
> 166
> 167 return 0;
> 168 }
> 169
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
prev parent reply other threads:[~2021-10-13 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 20:39 [jic23-iio:testing 149/151] drivers/iio/buffer/kfifo_buf.c:165:9: sparse: sparse: cast to restricted __poll_t kernel test robot
2021-10-13 17:40 ` Jonathan Cameron [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=20211013184001.00005b76@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexandru.ardelean@analog.com \
--cc=kbuild-all@lists.01.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mihail.chindris@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