From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Arnaud Ebalard <arno@natisbad.org>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: Drop owner assignment from platform_driver
Date: Fri, 10 Jul 2015 08:30:34 +0200 [thread overview]
Message-ID: <20150710083034.0429f147@bbrezillon> (raw)
In-Reply-To: <1436507176-27632-1-git-send-email-k.kozlowski@samsung.com>
On Fri, 10 Jul 2015 14:46:16 +0900
Krzysztof Kozlowski <k.kozlowski@samsung.com> wrote:
> platform_driver does not need to set an owner because
> platform_driver_register() will set it.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> ---
>
> The coccinelle script which generated the patch was sent here:
> http://www.spinics.net/lists/kernel/msg2029903.html
> ---
> drivers/crypto/marvell/cesa.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/crypto/marvell/cesa.c b/drivers/crypto/marvell/cesa.c
> index 1c6f98dd88f4..0643e3366e33 100644
> --- a/drivers/crypto/marvell/cesa.c
> +++ b/drivers/crypto/marvell/cesa.c
> @@ -533,7 +533,6 @@ static struct platform_driver marvell_cesa = {
> .probe = mv_cesa_probe,
> .remove = mv_cesa_remove,
> .driver = {
> - .owner = THIS_MODULE,
> .name = "marvell-cesa",
> .of_match_table = mv_cesa_of_match_table,
> },
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-10 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 5:46 [PATCH] crypto: Drop owner assignment from platform_driver Krzysztof Kozlowski
2015-07-10 6:30 ` Boris Brezillon [this message]
2015-07-14 7:01 ` Herbert Xu
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=20150710083034.0429f147@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=arno@natisbad.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=k.kozlowski@samsung.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vladimir_zapolskiy@mentor.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).