linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Timur Tabi <timur@kernel.org>, Xiubo Li <Xiubo.Lee@gmail.com>,
	tiwai@suse.de,
	"open list:FREESCALE SOC SOUND DRIVERS"
	<linuxppc-dev@lists.ozlabs.org>, Takashi Iwai <tiwai@suse.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Nicolin Chen <nicoleotsuka@gmail.com>,
	broonie@kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Fabio Estevam <festevam@gmail.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 4/6] ASoC: fsl: fsl_spdif: fix kernel-doc
Date: Thu,  2 Jul 2020 12:22:25 -0500	[thread overview]
Message-ID: <20200702172227.164474-5-pierre-louis.bossart@linux.intel.com> (raw)
In-Reply-To: <20200702172227.164474-1-pierre-louis.bossart@linux.intel.com>

Fix W=1 warnings. kernel-doc syntax was not followed and missing parameter

Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
 sound/soc/fsl/fsl_spdif.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/sound/soc/fsl/fsl_spdif.c b/sound/soc/fsl/fsl_spdif.c
index 5b2689ae63d4..9fb95c6ee7ba 100644
--- a/sound/soc/fsl/fsl_spdif.c
+++ b/sound/soc/fsl/fsl_spdif.c
@@ -81,8 +81,8 @@ struct spdif_mixer_control {
 };
 
 /**
- * fsl_spdif_priv: Freescale SPDIF private data
- *
+ * struct fsl_spdif_priv - Freescale SPDIF private data
+ * @soc: SPDIF soc data
  * @fsl_spdif_control: SPDIF control data
  * @cpu_dai_drv: cpu dai driver
  * @pdev: platform device pointer
@@ -100,6 +100,7 @@ struct spdif_mixer_control {
  * @spbaclk: SPBA clock (optional, depending on SoC design)
  * @dma_params_tx: DMA parameters for transmit channel
  * @dma_params_rx: DMA parameters for receive channel
+ * @regcache_srpc: regcache for SRPC
  */
 struct fsl_spdif_priv {
 	const struct fsl_spdif_soc_data *soc;
-- 
2.25.1


  parent reply	other threads:[~2020-07-02 17:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200702172227.164474-1-pierre-louis.bossart@linux.intel.com>
2020-07-02 17:22 ` [PATCH 1/6] ASoC: fsl: fsl_ssi_dbg: remove spurious kernel-doc comment start Pierre-Louis Bossart
2020-07-02 18:43   ` Nicolin Chen
2020-07-02 17:22 ` [PATCH 2/6] ASoC: fsl: fsl_ssi: fix kernel-doc Pierre-Louis Bossart
2020-07-02 18:44   ` Nicolin Chen
2020-07-02 17:22 ` [PATCH 3/6] ASoC: fsl: fsl-asoc-card: " Pierre-Louis Bossart
2020-07-02 18:47   ` Nicolin Chen
2020-07-02 19:03     ` Pierre-Louis Bossart
2020-07-02 17:22 ` Pierre-Louis Bossart [this message]
2020-07-02 18:48   ` [PATCH 4/6] ASoC: fsl: fsl_spdif: " Nicolin Chen
2020-07-02 17:22 ` [PATCH 5/6] ASoC: fsl: fsl_asrc: " Pierre-Louis Bossart
2020-07-02 18:51   ` Nicolin Chen
2020-07-02 17:22 ` [PATCH 6/6] ASoC: fsl: fsl_esai: " Pierre-Louis Bossart
2020-07-02 18:55   ` Nicolin Chen
2020-07-02 19:03     ` Pierre-Louis Bossart

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=20200702172227.164474-5-pierre-louis.bossart@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=timur@kernel.org \
    --cc=tiwai@suse.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).