From: Stanley Chu <stanley.chu@mediatek.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
kernel-janitors@vger.kernel.org,
Avri Altman <avri.altman@wdc.com>,
linux-mediatek@lists.infradead.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] scsi: ufs-mediatek: Fix platform_no_drv_owner.cocci warnings
Date: Thu, 21 Mar 2019 14:07:52 +0800 [thread overview]
Message-ID: <1553148472.30977.82.camel@mtkswgap22> (raw)
In-Reply-To: <20190321014517.11552-1-yuehaibing@huawei.com>
Hi,
On Thu, 2019-03-21 at 01:45 +0000, YueHaibing wrote:
> Remove .owner field if calls are used which set it automatically
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/scsi/ufs/ufs-mediatek.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/scsi/ufs/ufs-mediatek.c b/drivers/scsi/ufs/ufs-mediatek.c
> index c3b78fc83d3f..e9590bff5b5c 100644
> --- a/drivers/scsi/ufs/ufs-mediatek.c
> +++ b/drivers/scsi/ufs/ufs-mediatek.c
> @@ -358,7 +358,6 @@ static struct platform_driver ufs_mtk_pltform = {
> .shutdown = ufshcd_pltfrm_shutdown,
> .driver = {
> .name = "ufshcd-mtk",
> - .owner = THIS_MODULE,
> .pm = &ufs_mtk_pm_ops,
> .of_match_table = ufs_mtk_of_match,
> },
>
>
This is redundant currently. Thanks for helping removing it.
Reviewed-by: Stanley Chu <stanley.chu@mediatek.com>
Thanks,
Stanley
next prev parent reply other threads:[~2019-03-21 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 1:45 [PATCH -next] scsi: ufs-mediatek: Fix platform_no_drv_owner.cocci warnings YueHaibing
2019-03-21 6:07 ` Stanley Chu [this message]
2019-03-26 2:07 ` Martin K. Petersen
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=1553148472.30977.82.camel@mtkswgap22 \
--to=stanley.chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=pedrom.sousa@synopsys.com \
--cc=yuehaibing@huawei.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).