From: Stephen Boyd <sboyd@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Michael Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: fix platform_no_drv_owner.cocci warnings
Date: Wed, 28 Jan 2015 12:51:05 -0800 [thread overview]
Message-ID: <54C94BB9.4080008@codeaurora.org> (raw)
In-Reply-To: <20150128071134.GA6246@waimea>
On 01/27/15 23:11, kbuild test robot wrote:
> drivers/clk/qcom/lcc-msm8960.c:577:3-8: No need to set .owner here. The core will do it.
>
> Remove .owner field if calls are used which set it automatically
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
>
> CC: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-01-28 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201501281524.xeH8VSKz%fengguang.wu@intel.com>
2015-01-28 7:11 ` [PATCH] clk: qcom: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-01-28 20:51 ` Stephen Boyd [this message]
2015-02-25 20:02 ` Mike Turquette
2015-11-05 23:32 [PATCH 2/5] clk: qcom: Add IPQ4019 Global Clock Controller support kbuild test robot
2015-11-05 22:07 ` Matthew McClintock
2015-11-05 23:32 ` [PATCH] clk: qcom: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-11-05 23:32 ` kbuild test robot
[not found] <201501281508.7qdKuDxn%fengguang.wu@intel.com>
2015-01-28 7:00 ` kbuild test robot
2015-01-28 20:49 ` Stephen Boyd
2015-02-25 20:03 ` Mike Turquette
[not found] <201412090635.301ctah3%fengguang.wu@intel.com>
2014-12-08 22:21 ` kbuild test robot
[not found] <201412090645.oUKgIUsF%fengguang.wu@intel.com>
2014-12-08 22:07 ` 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=54C94BB9.4080008@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.