From: Paul Cercueil <paul@crapouillou.net>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: od@zcrc.me, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ASoC: jz4740-i2s: Make probe function __init_or_module
Date: Sat, 08 Jun 2019 12:24:25 +0200 [thread overview]
Message-ID: <1559989465.1815.8@crapouillou.net> (raw)
In-Reply-To: <20190607161500.17379-1-paul@crapouillou.net>
I misunderstood what __init_or_module was for. Please ignore this
patchset. Sorry for the noise.
Le ven. 7 juin 2019 à 18:14, Paul Cercueil <paul@crapouillou.net> a
écrit :
> This allows the probe function to be dropped after the kernel finished
> its initialization, in the case where the driver was not compiled as a
> module.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> ---
> sound/soc/jz4740/jz4740-i2s.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/jz4740/jz4740-i2s.c
> b/sound/soc/jz4740/jz4740-i2s.c
> index 13408de34055..1f596770b01a 100644
> --- a/sound/soc/jz4740/jz4740-i2s.c
> +++ b/sound/soc/jz4740/jz4740-i2s.c
> @@ -492,7 +492,7 @@ static const struct of_device_id
> jz4740_of_matches[] = {
> MODULE_DEVICE_TABLE(of, jz4740_of_matches);
> #endif
>
> -static int jz4740_i2s_dev_probe(struct platform_device *pdev)
> +static int __init_or_module jz4740_i2s_dev_probe(struct
> platform_device *pdev)
> {
> struct jz4740_i2s *i2s;
> struct resource *mem;
> --
> 2.21.0.593.g511ec345e18
>
prev parent reply other threads:[~2019-06-08 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 16:14 [PATCH 1/3] ASoC: jz4740-i2s: Make probe function __init_or_module Paul Cercueil
2019-06-07 16:14 ` [PATCH 2/3] ASoC/codecs: jz4740: " Paul Cercueil
2019-06-07 16:15 ` [PATCH 3/3] ASoC/codecs: jz4725b: " Paul Cercueil
2019-06-08 10:24 ` Paul Cercueil [this message]
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=1559989465.1815.8@crapouillou.net \
--to=paul@crapouillou.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=od@zcrc.me \
/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