From: kbuild test robot <lkp@intel.com>
To: Matthew Blecker <matthewb@chromium.org>,
Wolfram Sang <wsa-dev@sang-engineering.com>,
linux-i2c@vger.kernel.org
Cc: kbuild-all@lists.01.org, Matthew Blecker <matthewb@chromium.org>
Subject: Re: [PATCH 1/1] i2c: Add i2c-pseudo driver for userspace I2C adapters.
Date: Sat, 9 May 2020 09:43:30 +0800 [thread overview]
Message-ID: <202005090940.DjgfwRg4%lkp@intel.com> (raw)
In-Reply-To: <20200507230513.246804-2-matthewb@google.com>
Hi Matthew,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v5.7-rc4 next-20200508]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Matthew-Blecker/i2c-Add-i2c-pseudo-driver-for-userspace-I2C-adapters/20200509-011221
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
coccinelle warnings: (new ones prefixed by >>)
>> drivers/i2c/i2c-pseudo.c:2897:8-15: WARNING opportunity for memdup_user
--
>> drivers/i2c/i2c-pseudo.c:2206:1-17: ERROR: i2cp_fileops: .read() can deadlock .write(); change nonseekable_open -> stream_open to fix.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/1] i2c: Add i2c-pseudo driver for userspace I2C adapters.
Date: Sat, 09 May 2020 09:43:30 +0800 [thread overview]
Message-ID: <202005090940.DjgfwRg4%lkp@intel.com> (raw)
In-Reply-To: <20200507230513.246804-2-matthewb@google.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Hi Matthew,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v5.7-rc4 next-20200508]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Matthew-Blecker/i2c-Add-i2c-pseudo-driver-for-userspace-I2C-adapters/20200509-011221
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
coccinelle warnings: (new ones prefixed by >>)
>> drivers/i2c/i2c-pseudo.c:2897:8-15: WARNING opportunity for memdup_user
--
>> drivers/i2c/i2c-pseudo.c:2206:1-17: ERROR: i2cp_fileops: .read() can deadlock .write(); change nonseekable_open -> stream_open to fix.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2020-05-09 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 23:05 [PATCH 0/1] i2c: Add i2c-pseudo driver for userspace I2C adapters Matthew Blecker
2020-05-07 23:05 ` [PATCH 1/1] " Matthew Blecker
2020-05-08 20:36 ` kbuild test robot
2020-05-08 20:36 ` kbuild test robot
2020-05-09 1:43 ` kbuild test robot [this message]
2020-05-09 1:43 ` kbuild test robot
2020-05-09 1:43 ` [PATCH] i2c: fix stream_open.cocci warnings kbuild test robot
2020-05-09 1:43 ` kbuild test robot
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=202005090940.DjgfwRg4%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=matthewb@chromium.org \
--cc=wsa-dev@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.