From: kbuild test robot <lkp@intel.com>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org,
Purna Chandra Mandal <purna.mandal@microchip.com>,
Mark Brown <broonie@kernel.org>,
Joshua Henderson <digitalpeer@digitalpeer.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH v2 2/2] spi: spi-pic32: Add PIC32 SPI master driver
Date: Fri, 4 Mar 2016 23:22:38 +0800 [thread overview]
Message-ID: <201603042319.6opKQQ8d%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457099082-12587-2-git-send-email-purna.mandal@microchip.com>
Hi Purna,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.5-rc6 next-20160303]
[cannot apply to spi/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Purna-Chandra-Mandal/dt-bindings-Add-bindings-for-PIC32-SPI-peripheral/20160304-214814
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux for-next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/spi/spi-pic32.c:993: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 prev parent reply other threads:[~2016-03-04 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 13:44 [PATCH v2 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal
2016-03-04 13:44 ` [PATCH v2 2/2] spi: spi-pic32: Add PIC32 SPI master driver Purna Chandra Mandal
2016-03-04 15:22 ` [PATCH] spi: spi-pic32: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-03-04 15:22 ` kbuild test robot [this message]
2016-03-05 3:40 ` [PATCH v2 2/2] spi: spi-pic32: Add PIC32 SPI master driver Mark Brown
2016-03-05 15:15 ` Purna Chandra Mandal
2016-03-06 2:25 ` Mark Brown
2016-03-05 6:36 ` kbuild test robot
2016-03-05 4:31 ` [PATCH v2 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Rob Herring
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=201603042319.6opKQQ8d%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=digitalpeer@digitalpeer.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=purna.mandal@microchip.com \
--cc=sergei.shtylyov@cogentembedded.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
all inboxes | Powered by JetHome®