mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: kbuild-all@01.org, Alessandro Zummo <a.zummo@towertech.it>,
	rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: drivers/rtc/rtc-rv8803.c:494:3-8: No need to set .owner here. The core will do it.
Date: Sat, 26 Sep 2015 22:42:07 +0800	[thread overview]
Message-ID: <201509262245.qTOvBbXQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443275679-21459-1-git-send-email-alexandre.belloni@free-electrons.com>

Hi Alexandre,

FYI, build test results on v4.3-rc2 (pls ignore if it's inappropriate base for your patch).


coccinelle warnings: (new ones prefixed by >>)

>> drivers/rtc/rtc-rv8803.c:494:3-8: No need to set .owner here. The core will do it.
--
>> drivers/rtc/rtc-rv8803.c:350:2-5: WARNING: end returns can be simpified if negative or 0 value

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

  parent reply	other threads:[~2015-09-26 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26 13:54 [PATCH] rtc: Add a driver for Micro Crystal RV8803 Alexandre Belloni
2015-09-26 14:42 ` [PATCH] rtc: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-09-26 14:42 ` kbuild test robot [this message]
2015-09-28  3:04 ` [PATCH] rtc: Add a driver for Micro Crystal RV8803 Josh Cartwright
2015-09-28  6:16 ` [PATCH] rtc: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-09-28  6:16 ` [PATCH] rtc: Add a driver for Micro Crystal RV8803 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=201509262245.qTOvBbXQ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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®