From: srishtishar@gmail.com (srishti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue
Date: Thu, 18 May 2017 15:37:48 +0530 [thread overview]
Message-ID: <1495102068-3288-1-git-send-email-srishtishar@gmail.com> (raw)
Fixed a trailing */ issue.
Signed-off-by: srishti <srishtishar@gmail.com>
---
drivers/staging/bcm2835-audio/bcm2835-ctl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/bcm2835-audio/bcm2835-ctl.c b/drivers/staging/bcm2835-audio/bcm2835-ctl.c
index a4ffa1b..38fabab 100644
--- a/drivers/staging/bcm2835-audio/bcm2835-ctl.c
+++ b/drivers/staging/bcm2835-audio/bcm2835-ctl.c
@@ -247,8 +247,8 @@ static int snd_bcm2835_spdif_mask_get(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_value *ucontrol)
{
/* bcm2835 supports only consumer mode and sets all other format flags
- * automatically. So the only thing left is signalling non-audio
- * content */
+ * automatically. So the only thing left is signalling non-audio content
+ */
ucontrol->value.iec958.status[0] = IEC958_AES0_NONAUDIO;
return 0;
}
2.7.4
next reply other threads:[~2017-05-18 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 10:07 srishti [this message]
2017-05-18 10:13 ` [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue Dan Carpenter
2017-05-18 10:42 srishti
2017-05-18 10:50 srishti
2017-05-18 13:58 ` Greg KH
2017-05-19 19:30 ` srishti sharma
2017-05-19 19:33 ` Dan Carpenter
2017-05-19 19:56 ` srishti sharma
2017-05-19 20:30 srishti sharma
2017-05-25 16:57 ` Greg KH
2017-05-25 19:27 ` srishti sharma
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=1495102068-3288-1-git-send-email-srishtishar@gmail.com \
--to=srishtishar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).