linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Vinod Koul <vinod.koul@intel.com>, Mark Brown <broonie@kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	rostedt@goodmis.org, John Kacur <jkacur@redhat.com>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	alsa-devel@alsa-project.org, Jie Yang <yang.jie@intel.com>
Subject: [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement
Date: Thu, 11 Jun 2015 14:22:27 +0200	[thread overview]
Message-ID: <20150611122227.GF16115@linutronix.de> (raw)
In-Reply-To: <55623BC2.80307@localhost>

This was spotted by Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
while he tried to compile a -RT kernel with this driver enabled.
"make C=2" would also warn about this. This is is based on his patch.

Reported-by: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 sound/soc/intel/atom/sst/sst.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sound/soc/intel/atom/sst/sst.c b/sound/soc/intel/atom/sst/sst.c
index 96c2e420cce6..b0c3e0e56302 100644
--- a/sound/soc/intel/atom/sst/sst.c
+++ b/sound/soc/intel/atom/sst/sst.c
@@ -368,8 +368,8 @@ static inline void sst_restore_shim64(struct intel_sst_drv *ctx,
 	 * initialize by FW or driver when firmware is loaded
 	 */
 	spin_lock_irqsave(&ctx->ipc_spin_lock, irq_flags);
-	sst_shim_write64(shim, SST_IMRX, shim_regs->imrx),
-	sst_shim_write64(shim, SST_CSR, shim_regs->csr),
+	sst_shim_write64(shim, SST_IMRX, shim_regs->imrx):
+	sst_shim_write64(shim, SST_CSR, shim_regs->csr);
 	spin_unlock_irqrestore(&ctx->ipc_spin_lock, irq_flags);
 }
 
-- 
2.1.4

  reply	other threads:[~2015-06-11 12:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51   ` Pavel Vasilyev
2015-05-20  7:12   ` Sebastian Andrzej Siewior
2015-05-20 13:18   ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20  3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09   ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08   ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22   ` Sebastian Andrzej Siewior [this message]
2015-06-11 13:04     ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Mats Karrman
2015-06-11 13:14       ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12  7:22         ` Vinod Koul
2015-06-12 10:37         ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38   ` Steven Rostedt
2015-05-26 13:48     ` Clark Williams
2015-05-26 14:49       ` Mike Galbraith
2015-05-26 15:19       ` Steven Rostedt
2015-05-26 15:43         ` Clark Williams
2015-05-26 19:41           ` Fernando Lopez-Lezcano
2015-05-29  1:56             ` Fernando Lopez-Lezcano
2015-06-09 16:45               ` Fernando Lopez-Lezcano
2015-06-09 22:05                 ` Pavel Vasilyev
2015-06-10  2:41                   ` Mike Galbraith
2015-06-10  3:10                   ` Fernando Lopez-Lezcano
2015-06-09 22:10                 ` Pavel Vasilyev
2015-06-11 12:38               ` Sebastian Andrzej Siewior
2015-05-28  8:41           ` Joakim Hernberg
2015-06-11 12:34           ` Sebastian Andrzej Siewior
2015-05-27  9:44 ` Joakim Hernberg
2015-05-27 10:19   ` Jeremy Jongepier
2015-05-28  8:33     ` Joakim Hernberg
2015-05-27 15:50   ` Ralf Mardorf

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=20150611122227.GF16115@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vinod.koul@intel.com \
    --cc=yang.jie@intel.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).