From: Mark Brown <broonie@kernel.org> To: YueHaibing <yuehaibing@huawei.com> Cc: Axel Lin <axel.lin@ingics.com>, kernel-janitors@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>, Robert Marko <robert.marko@sartura.hr> Subject: Applied "regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings" to the regulator tree Date: Fri, 17 Jan 2020 15:44:18 +0000 (GMT) [thread overview] Message-ID: <applied-20200116023344.163592-1-yuehaibing@huawei.com> (raw) In-Reply-To: <20200116023344.163592-1-yuehaibing@huawei.com> The patch regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.6 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark From 493a31ee0dbdb58d23aa3b06da2da7901f55f76b Mon Sep 17 00:00:00 2001 From: YueHaibing <yuehaibing@huawei.com> Date: Thu, 16 Jan 2020 02:33:44 +0000 Subject: [PATCH] regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings 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> Link: https://lore.kernel.org/r/20200116023344.163592-1-yuehaibing@huawei.com Signed-off-by: Mark Brown <broonie@kernel.org> --- drivers/regulator/vqmmc-ipq4019-regulator.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/regulator/vqmmc-ipq4019-regulator.c b/drivers/regulator/vqmmc-ipq4019-regulator.c index 685b585b39a1..6d5ae25d08d1 100644 --- a/drivers/regulator/vqmmc-ipq4019-regulator.c +++ b/drivers/regulator/vqmmc-ipq4019-regulator.c @@ -91,7 +91,6 @@ static struct platform_driver ipq4019_regulator_driver = { .probe = ipq4019_regulator_probe, .driver = { .name = "vqmmc-ipq4019-regulator", - .owner = THIS_MODULE, .of_match_table = of_match_ptr(regulator_ipq4019_of_match), }, }; -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: YueHaibing <yuehaibing@huawei.com> Cc: Axel Lin <axel.lin@ingics.com>, kernel-janitors@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>, Robert Marko <robert.marko@sartura.hr> Subject: Applied "regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings" to the regulator tree Date: Fri, 17 Jan 2020 15:44:18 +0000 [thread overview] Message-ID: <applied-20200116023344.163592-1-yuehaibing@huawei.com> (raw) In-Reply-To: <20200116023344.163592-1-yuehaibing@huawei.com> The patch regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.6 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark From 493a31ee0dbdb58d23aa3b06da2da7901f55f76b Mon Sep 17 00:00:00 2001 From: YueHaibing <yuehaibing@huawei.com> Date: Thu, 16 Jan 2020 02:33:44 +0000 Subject: [PATCH] regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings 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> Link: https://lore.kernel.org/r/20200116023344.163592-1-yuehaibing@huawei.com Signed-off-by: Mark Brown <broonie@kernel.org> --- drivers/regulator/vqmmc-ipq4019-regulator.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/regulator/vqmmc-ipq4019-regulator.c b/drivers/regulator/vqmmc-ipq4019-regulator.c index 685b585b39a1..6d5ae25d08d1 100644 --- a/drivers/regulator/vqmmc-ipq4019-regulator.c +++ b/drivers/regulator/vqmmc-ipq4019-regulator.c @@ -91,7 +91,6 @@ static struct platform_driver ipq4019_regulator_driver = { .probe = ipq4019_regulator_probe, .driver = { .name = "vqmmc-ipq4019-regulator", - .owner = THIS_MODULE, .of_match_table = of_match_ptr(regulator_ipq4019_of_match), }, }; -- 2.20.1
next prev parent reply other threads:[~2020-01-17 15:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-16 2:33 [PATCH -next] regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings YueHaibing 2020-01-16 2:33 ` YueHaibing 2020-01-17 15:44 ` Mark Brown [this message] 2020-01-17 15:44 ` Applied "regulator: vqmmc-ipq4019: Fix platform_no_drv_owner.cocci warnings" to the regulator tree Mark Brown
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=applied-20200116023344.163592-1-yuehaibing@huawei.com \ --to=broonie@kernel.org \ --cc=axel.lin@ingics.com \ --cc=kernel-janitors@vger.kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=robert.marko@sartura.hr \ --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: linkBe 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.