From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: nicoleotsuka@gmail.com,
Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, lars@metafoo.de, timur@tabi.org
Subject: Re: [PATCH] ASoC: fsl_ssi: Remove custom fsl_ssi_debugfs_create/remove()
Date: Wed, 8 Apr 2015 17:59:46 +0100 [thread overview]
Message-ID: <20150408165946.GC6023@sirena.org.uk> (raw)
In-Reply-To: <1428512062-17229-1-git-send-email-festevam@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 973 bytes --]
On Wed, Apr 08, 2015 at 01:54:22PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Since commit 81c7cfd1b22a0 ("ASoC: Move debugfs registration to the
> component level") ASoC core code deals with registering debugfs, so we
> should remove the custom fsl_ssi_debugfs_create/remove() to avoid the
> following warning:
So this sounds like an issue but...
> -int fsl_ssi_debugfs_create(struct fsl_ssi_dbg *ssi_dbg, struct device *dev)
> -{
> - ssi_dbg->dbg_dir = debugfs_create_dir(dev_name(dev), NULL);
> - if (!ssi_dbg->dbg_dir)
> - return -ENOMEM;
> -
> - ssi_dbg->dbg_stats = debugfs_create_file("stats", S_IRUGO,
> - ssi_dbg->dbg_dir, ssi_dbg, &fsl_ssi_stats_ops);
> - if (!ssi_dbg->dbg_stats) {
> - debugfs_remove(ssi_dbg->dbg_dir);
> - return -ENOMEM;
> - }
> -
> - return 0;
> -}
...shouldn't this just be removing the creation of the directory, not
the stats file that was being put inside it?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-04-08 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:54 [PATCH] ASoC: fsl_ssi: Remove custom fsl_ssi_debugfs_create/remove() Fabio Estevam
2015-04-08 16:59 ` Mark Brown [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=20150408165946.GC6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--cc=nicoleotsuka@gmail.com \
--cc=timur@tabi.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