Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, vkoul@kernel.org
Subject: Re: [PATCH v2] ALSA: hda: fix kernel-doc warnings
Date: Tue, 02 Mar 2021 10:21:49 +0100	[thread overview]
Message-ID: <s5hmtvlhpw2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210301174617.116960-1-pierre-louis.bossart@linux.intel.com>

On Mon, 01 Mar 2021 18:46:17 +0100,
Pierre-Louis Bossart wrote:
> 
> v5.12-rc1 flags new warnings with make W=1, fix missing or broken
> function descriptors.
> 
> sound/pci/hda/hda_codec.c:3492: warning: expecting prototype for
> snd_hda_input_mux_info_info(). Prototype was for
> snd_hda_input_mux_info() instead
> 
> sound/pci/hda/hda_codec.c:3521: warning: expecting prototype for
> snd_hda_input_mux_info_put(). Prototype was for
> snd_hda_input_mux_put() instead
> 
> sound/pci/hda/hda_codec.c:3958: warning: expecting prototype for
> _snd_hda_pin_ctl(). Prototype was for _snd_hda_set_pin_ctl() instead
> 
> sound/pci/hda/hda_jack.c:223: warning: expecting prototype for
> snd_hda_set_dirty_all(). Prototype was for
> snd_hda_jack_set_dirty_all() instead
> 
> sound/pci/hda/hda_jack.c:309: warning: expecting prototype for
> snd_hda_jack_detect_enable_mst(). Prototype was for
> snd_hda_jack_detect_enable_callback_mst() instead
> 
> sound/pci/hda/hda_generic.c:3933: warning: expecting prototype for
> snd_dha_gen_add_mute_led_cdev(). Prototype was for
> snd_hda_gen_add_mute_led_cdev() instead
> 
> sound/pci/hda/hda_generic.c:4093: warning: expecting prototype for
> snd_dha_gen_add_micmute_led_cdev(). Prototype was for
> snd_hda_gen_add_micmute_led_cdev() instead
> 
> sound/pci/hda/patch_ca0132.c:2357: warning: expecting prototype for
> Prepare and send the SCP message to DSP(). Prototype was for
> dspio_scp() instead
> 
> sound/pci/hda/patch_ca0132.c:2883: warning: expecting prototype for
> Allocate router ports(). Prototype was for dsp_allocate_router_ports()
> instead
> 
> sound/pci/hda/patch_ca0132.c:3202: warning: expecting prototype for
> Write a block of data into DSP code or data RAM using pre(). Prototype
> was for dspxfr_one_seg() instead
> 
> sound/pci/hda/patch_ca0132.c:3397: warning: expecting prototype for
> data overlay to DSP memories(). Prototype was for dspxfr_image()
> instead
> 
> sound/hda/hdac_regmap.c:393: warning: expecting prototype for
> snd_hdac_regmap_init(). Prototype was for snd_hdac_regmap_exit()
> instead
> 
> sound/hda/ext/hdac_ext_controller.c:142: warning: expecting prototype
> for snd_hdac_ext_bus_get_link_index(). Prototype was for
> snd_hdac_ext_bus_get_link() instead
> 
> sound/hda/ext/hdac_ext_stream.c:140: warning: expecting prototype for
> snd_hdac_ext_linkstream_start(). Prototype was for
> snd_hdac_ext_link_stream_start() instead
> 
> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

Thanks, applied.


Takashi

      reply	other threads:[~2021-03-02  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 17:46 [PATCH v2] ALSA: hda: fix kernel-doc warnings Pierre-Louis Bossart
2021-03-02  9:21 ` Takashi Iwai [this message]

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=s5hmtvlhpw2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=vkoul@kernel.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