All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
	alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: ASoC: Failed to create component debugfs directory
Date: Wed, 21 Feb 2018 10:47:45 -0300	[thread overview]
Message-ID: <CAOMZO5B_H0EN7c8+dCwuXvP3_KOoLz=94KQO9oZOM9PoeMX-1A@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5DZ0W5q6OAvrRWv+8GNbWn5ttLk3q035H=4fLton-1mgg@mail.gmail.com>

On Wed, Feb 21, 2018 at 10:43 AM, Fabio Estevam <festevam@gmail.com> wrote:

> Had to change it to pcm->component.name_prefix = "dma"; but still see
> the warnings.

Looks like this can fix it:

--- a/sound/soc/soc-generic-dmaengine-pcm.c
+++ b/sound/soc/soc-generic-dmaengine-pcm.c
@@ -442,6 +442,7 @@ int snd_dmaengine_pcm_register(struct device *dev,
        if (!pcm)
                return -ENOMEM;

+       pcm->component.debugfs_prefix = "dma";
        pcm->config = config;
        pcm->flags = flags;

Would you like me to submit it?

Thanks

  reply	other threads:[~2018-02-21 13:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 18:49 ASoC: Failed to create component debugfs directory Fabio Estevam
2018-02-19 20:14 ` Nicolin Chen
2018-02-20 11:47   ` Mark Brown
2018-02-20 14:18 ` Fabio Estevam
2018-02-20 14:24   ` Lars-Peter Clausen
2018-02-20 19:26     ` Fabio Estevam
2018-02-20 19:30       ` Lars-Peter Clausen
2018-02-20 19:37         ` Fabio Estevam
2018-02-21 13:02           ` Mark Brown
2018-02-21 13:43             ` Fabio Estevam
2018-02-21 13:47               ` Fabio Estevam [this message]
2018-02-21 14:40                 ` Mark Brown
2018-02-20 16:40   ` Fabio Estevam
2018-02-20 18:37 ` Srinivas Kandagatla
2018-02-20 18:43   ` Fabio Estevam

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='CAOMZO5B_H0EN7c8+dCwuXvP3_KOoLz=94KQO9oZOM9PoeMX-1A@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=nicoleotsuka@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.