From: kbuild test robot <lkp@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kbuild-all@01.org, MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org,
David Cohen <david.a.cohen@intel.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] extcon: 3gpio: add driver for USB OTG port controlled by 3 GPIOs
Date: Mon, 19 Dec 2016 10:01:49 +0800 [thread overview]
Message-ID: <201612190940.6mZzYmlb%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161219001220.13321-1-hdegoede@redhat.com>
Hi David,
[auto build test WARNING on chanwoo-extcon/extcon-next]
[also build test WARNING on v4.9 next-20161216]
[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/Hans-de-Goede/extcon-3gpio-add-driver-for-USB-OTG-port-controlled-by-3-GPIOs/20161219-082834
base: https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git extcon-next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/extcon/extcon-3gpio_otg.c:190: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-12-19 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 2:01 kbuild test robot [this message]
2016-12-19 0:12 ` [PATCH] extcon: 3gpio: add driver for USB OTG port controlled by 3 GPIOs Hans de Goede
2016-12-19 1:57 ` kbuild test robot
2016-12-19 2:01 ` [PATCH] extcon: 3gpio: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-12-19 2:34 ` [PATCH] extcon: 3gpio: add driver for USB OTG port controlled by 3 GPIOs kbuild test robot
2016-12-19 8:00 ` Chanwoo Choi
2016-12-19 8:57 ` Hans de Goede
2016-12-19 9:41 ` Chanwoo Choi
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=201612190940.6mZzYmlb%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cw00.choi@samsung.com \
--cc=david.a.cohen@intel.com \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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;
as well as URLs for NNTP newsgroup(s).