From: kbuild test robot <lkp@intel.com>
To: Daniel Baluta <daniel.baluta@intel.com>
Cc: kbuild-all@01.org, jic23@kernel.org, jlbec@evilplan.org,
linux-iio@vger.kernel.org, linux-fsdevel@vger.kernel.org,
lars@metafoo.de, hch@lst.de, knaack.h@gmx.de,
linux-kernel@vger.kernel.org, octavian.purdila@intel.com,
pebolle@tiscali.nl, patrick.porlan@intel.com,
adriana.reus@intel.com, constantin.musca@intel.com,
marten@intuitiveaerial.com, daniel.baluta@intel.com,
cristina.opriceana@gmail.com, pmeerw@pmeerw.net,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org
Subject: Re: [PATCH v10 3/5] iio: core: Introduce IIO software triggers
Date: Sat, 24 Oct 2015 00:38:37 +0800 [thread overview]
Message-ID: <201510240028.L0tyneYI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445614411-533-4-git-send-email-daniel.baluta@intel.com>
Hi Daniel,
[auto build test WARNING on next-20151022 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Daniel-Baluta/Add-initial-configfs-support-for-IIO/20151023-233520
coccinelle warnings: (new ones prefixed by >>)
>> drivers/iio/industrialio-sw-trigger.c:169:1-3: WARNING: PTR_ERR_OR_ZERO can be used
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
next prev parent reply other threads:[~2015-10-23 16:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 15:33 [PATCH v10 0/5] Add initial configfs support for IIO Daniel Baluta
2015-10-23 15:33 ` [PATCH v10 1/5] configfs: Allow dynamic group creation Daniel Baluta
2015-11-06 7:50 ` Christoph Hellwig
2015-11-06 8:48 ` Daniel Baluta
2015-11-06 9:31 ` Lars-Peter Clausen
[not found] ` <A334FE9C-F187-4304-AA98-6A40347AF731@jic23.retrosnub.co.uk>
2015-11-07 13:09 ` Christoph Hellwig
2015-11-08 15:30 ` Jonathan Cameron
2015-11-10 6:51 ` Christoph Hellwig
2015-11-10 21:12 ` Andrew Morton
2015-11-11 6:43 ` Jonathan Cameron
2015-11-15 10:39 ` Jonathan Cameron
2015-11-17 23:47 ` Andrew Morton
2015-11-18 7:33 ` Jonathan Cameron
2015-11-29 17:27 ` Jonathan Cameron
2015-12-02 18:32 ` Jonathan Cameron
2015-11-11 23:08 ` Joel Becker
2015-10-23 15:33 ` [PATCH v10 2/5] iio: core: Introduce IIO configfs support Daniel Baluta
2015-10-24 9:11 ` Matt Ranostay
2015-10-23 15:33 ` [PATCH v10 3/5] iio: core: Introduce IIO software triggers Daniel Baluta
2015-10-23 16:38 ` [PATCH] iio: core: fix ptr_ret.cocci warnings kbuild test robot
2015-10-23 16:38 ` kbuild test robot [this message]
2015-10-23 15:33 ` [PATCH v10 4/5] iio: trigger: Introduce IIO hrtimer based trigger Daniel Baluta
2015-10-23 15:33 ` [PATCH v10 5/5] iio: Documentation: Add IIO configfs documentation Daniel Baluta
2015-10-27 8:35 ` Crt Mori
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=201510240028.L0tyneYI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adriana.reus@intel.com \
--cc=akpm@linux-foundation.org \
--cc=constantin.musca@intel.com \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=hch@lst.de \
--cc=jic23@kernel.org \
--cc=jlbec@evilplan.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marten@intuitiveaerial.com \
--cc=octavian.purdila@intel.com \
--cc=patrick.porlan@intel.com \
--cc=pebolle@tiscali.nl \
--cc=pmeerw@pmeerw.net \
--cc=viro@zeniv.linux.org.uk \
/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).