mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: brgl@bgdev.pl, david@lechnology.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: regmap: Failed to create debugfs directory
Date: Mon, 5 Mar 2018 16:07:33 +0000	[thread overview]
Message-ID: <20180305160733.GM8588@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5DhpG+68CtrVR-nYbD3gjH5zoPiTqdz3NcUqSW5iJsOLg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

On Thu, Mar 01, 2018 at 03:28:37PM -0300, Fabio Estevam wrote:
> On Thu, Mar 1, 2018 at 3:19 PM, Fabio Estevam <festevam@gmail.com> wrote:

> > Running linux-next 20180301 on a imx6q-sabresd the following
> > regmap-debugfs warnings are seen:

> This only happens when the regmap name is 'dummy'.

> [    0.083651] vdd1p1: supplied by regulator-dummy
> [    0.084929] vdd3p0: supplied by regulator-dummy
> [    0.085974] vdd2p5: supplied by regulator-dummy
> [    0.110028] *****regmap name: dummy
> [    0.110090] (NULL device *): regmap*** Failed to create debugfs directory

Do we know what exactly is creating these debugfs entries?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-03-05 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 18:19 Fabio Estevam
2018-03-01 18:24 ` Mark Brown
2018-03-02  0:27   ` Fabio Estevam
2018-03-02 12:35     ` Fabio Estevam
2018-03-01 18:28 ` Fabio Estevam
2018-03-05 16:07   ` 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=20180305160733.GM8588@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=david@lechnology.com \
    --cc=festevam@gmail.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®