From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: gregkh@linuxfoundation.org
Cc: eric@anholt.net, stefan.wahren@i2se.com,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, tiwai@suse.de,
nsaenzjulienne@suse.de, devel@driverdev.osuosl.org
Subject: [PATCH v2 6/7] staging: bcm2835-audio: rename platform_driver structure
Date: Wed, 17 Oct 2018 21:01:55 +0200 [thread overview]
Message-ID: <20181017190156.30010-7-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20181017190156.30010-1-nsaenzjulienne@suse.de>
It was called bcm2835_alsa0_driver, that "0" didn't mean much.
Suggested-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
---
drivers/staging/vc04_services/bcm2835-audio/bcm2835.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/vc04_services/bcm2835-audio/bcm2835.c b/drivers/staging/vc04_services/bcm2835-audio/bcm2835.c
index 039565311d10..e14b7c5aa07c 100644
--- a/drivers/staging/vc04_services/bcm2835-audio/bcm2835.c
+++ b/drivers/staging/vc04_services/bcm2835-audio/bcm2835.c
@@ -343,7 +343,7 @@ static const struct of_device_id snd_bcm2835_of_match_table[] = {
};
MODULE_DEVICE_TABLE(of, snd_bcm2835_of_match_table);
-static struct platform_driver bcm2835_alsa0_driver = {
+static struct platform_driver bcm2835_alsa_driver = {
.probe = snd_bcm2835_alsa_probe,
#ifdef CONFIG_PM
.suspend = snd_bcm2835_alsa_suspend,
@@ -359,7 +359,7 @@ static int bcm2835_alsa_device_init(void)
{
int retval;
- retval = platform_driver_register(&bcm2835_alsa0_driver);
+ retval = platform_driver_register(&bcm2835_alsa_driver);
if (retval)
pr_err("Error registering bcm2835_audio driver %d .\n", retval);
@@ -368,7 +368,7 @@ static int bcm2835_alsa_device_init(void)
static void bcm2835_alsa_device_exit(void)
{
- platform_driver_unregister(&bcm2835_alsa0_driver);
+ platform_driver_unregister(&bcm2835_alsa_driver);
}
late_initcall(bcm2835_alsa_device_init);
--
2.19.1
next prev parent reply other threads:[~2018-10-17 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 19:01 [PATCH v2 0/7] staging: bcm2835-audio: Cleanups and upgrades Nicolas Saenz Julienne
2018-10-17 19:01 ` [PATCH v2 1/7] staging: bcm2835-audio: unify FOURCC command definitions Nicolas Saenz Julienne
2018-10-17 19:01 ` [PATCH v2 2/7] staging: bcm2835-audio: don't initialize memory twice Nicolas Saenz Julienne
2018-10-17 19:01 ` [PATCH v2 3/7] staging: bcm2835-audio: reorder variable declarations & remove trivial comments Nicolas Saenz Julienne
2018-10-17 19:01 ` [PATCH v2 4/7] staging: bcm2835-audio: use anonymous union in struct vc_audio_msg Nicolas Saenz Julienne
2018-10-17 19:01 ` [PATCH v2 5/7] staging: bcm2835-audio: more generic probe function name Nicolas Saenz Julienne
2018-10-17 19:01 ` Nicolas Saenz Julienne [this message]
2018-10-17 19:01 ` [PATCH v2 7/7] staging: bcm2835-audio: update TODO Nicolas Saenz Julienne
2018-10-18 18:07 ` [PATCH v2 0/7] staging: bcm2835-audio: Cleanups and upgrades Stefan Wahren
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=20181017190156.30010-7-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
--cc=tiwai@suse.de \
/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).