From: kbuild test robot <lkp@intel.com>
To: Patrick Vogelaar <Patrick.Vogelaar@gigatronik.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-input@vger.kernel.org,
Patrick Vogelaar <Patrick.Vogelaar@gigatronik.com>
Subject: Re: [PATCH 1/2] add driver for cypress cy8cmbr3102
Date: Mon, 20 Feb 2017 20:05:29 +0800 [thread overview]
Message-ID: <201702202015.pVoAzgsD%fengguang.wu@intel.com> (raw)
In-Reply-To: <1487586813-4122-2-git-send-email-Patrick.Vogelaar@gigatronik.com>
Hi Patrick,
[auto build test WARNING on input/next]
[also build test WARNING on v4.10 next-20170220]
[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/Patrick-Vogelaar/add-driver-for-cypress-cy8cmbr3102/20170220-185014
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/input/misc/cy8cmbr3102.c:210:4-9: 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 prev parent reply other threads:[~2017-02-20 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 10:33 [PATCH 0/2] add driver for cypress cy8cmbr3102 Patrick Vogelaar
2017-02-20 10:33 ` [PATCH 1/2] " Patrick Vogelaar
2017-02-20 12:05 ` kbuild test robot [this message]
2017-02-20 12:05 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-02-20 10:33 ` [PATCH 2/2] add device tree documentation for cy8cmbr3102 Patrick Vogelaar
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=201702202015.pVoAzgsD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Patrick.Vogelaar@gigatronik.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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