From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: alsa-devel@lists.sourceforge.net
Subject: [PATCH] ASoC very minor coding style fix for snd_soc_new_pcms()
Date: Wed, 31 Jan 2007 17:22:44 +0000 [thread overview]
Message-ID: <1170264164.16760.91.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 164 bytes --]
This very minor patch fixes the snd_soc_new_pcms() function to comply
with the kernel coding style.
Signed-off-by: Liam Girdwood <lg@opensource.wolfsonmicro.com>
[-- Attachment #2: asoc-new-pcm-style.patch --]
[-- Type: text/x-patch, Size: 509 bytes --]
diff -r 2a5adb550155 soc/soc-core.c
--- a/soc/soc-core.c Wed Jan 31 14:34:38 2007 +0100
+++ b/soc/soc-core.c Wed Jan 31 17:11:46 2007 +0000
@@ -1522,7 +1522,7 @@ EXPORT_SYMBOL_GPL(snd_soc_get_rate);
*
* Returns 0 for success, else error.
*/
-int snd_soc_new_pcms(struct snd_soc_device *socdev, int idx, const char * xid)
+int snd_soc_new_pcms(struct snd_soc_device *socdev, int idx, const char *xid)
{
struct snd_soc_codec *codec = socdev->codec;
struct snd_soc_machine *machine = socdev->machine;
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2007-01-31 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 17:22 Liam Girdwood [this message]
2007-02-01 11:28 ` [PATCH] ASoC very minor coding style fix for snd_soc_new_pcms() Takashi Iwai
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=1170264164.16760.91.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@lists.sourceforge.net \
/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