From: kbuild test robot <lkp@intel.com>
To: vadimp@mellanox.com
Cc: kbuild-all@01.org, wsa@the-dreams.de, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, jiri@resnulli.us,
Vadim Pasternak <vadimp@mellanox.com>,
Michael Shych <michaelsh@mellanox.com>
Subject: Re: [patch 2/2] i2c: mux: mellanox: add driver
Date: Thu, 25 Aug 2016 14:50:30 +0800 [thread overview]
Message-ID: <201608251408.feJ5zXcz%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472046988-111956-1-git-send-email-vadimp@mellanox.com>
Hi Vadim,
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.8-rc3 next-20160824]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/vadimp-mellanox-com/i2c-add-master-driver-for-mellanox-systems/20160824-200057
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/i2c/muxes/i2c-mux-mlxcpld.c:329:3-8: No need to set .owner here. The core will do it.
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 parent reply other threads:[~2016-08-25 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 6:50 kbuild test robot [this message]
2016-08-24 13:56 ` vadimp
2016-08-24 13:54 ` Peter Rosin
2016-08-24 16:20 ` Vadim Pasternak
2016-08-25 8:53 ` Peter Rosin
2016-08-25 10:08 ` Vadim Pasternak
2016-08-25 6:50 ` [PATCH] i2c: mux: mellanox: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-08-28 16:54 [patch 2/2] i2c: mux: mellanox: add driver vadimp
2016-08-28 20:42 ` kbuild test robot
2016-08-29 17:36 vadimp
2016-09-02 12:16 ` Peter Rosin
2016-09-06 11:00 ` Peter Rosin
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=201608251408.feJ5zXcz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jiri@resnulli.us \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=vadimp@mellanox.com \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®