From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
atull@opensource.altera.com
Subject: Re: [PATCH] regulator: of: Lower the severity of the error with no container
Date: Thu, 9 Oct 2014 10:49:58 -0700 [thread overview]
Message-ID: <20141009174958.GA4396@roeck-us.net> (raw)
In-Reply-To: <20141009155440.GV4609@sirena.org.uk>
On Thu, Oct 09, 2014 at 04:54:40PM +0100, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 05:25:31PM -0700, Guenter Roeck wrote:
>
> > > Shove a dev_name() on the front if we get a collision? I have to say
> > > I've never cared, the debugfs isn't that important so it doesn't matter
> > > too much if it fails.
>
> > Sure, but, again, I am getting lots and lots of those error messages.
> > I probably would not care either (and probably not even have noticed)
> > if not for those messages.
>
> > Want me to submit a patch with the dev_name solution ?
>
> Yes, please.
Turns out that is already supposed to happen if the function creating
the entry knows about the device. I guess this explains why others don't
see the problem. We'll have to find out what is going on.
Guenter
prev parent reply other threads:[~2014-10-09 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 22:09 [PATCH] regulator: of: Lower the severity of the error with no container Mark Brown
2014-10-08 22:34 ` Guenter Roeck
2014-10-08 22:36 ` Mark Brown
2014-10-08 22:59 ` Guenter Roeck
2014-10-08 23:45 ` Mark Brown
2014-10-09 0:05 ` Guenter Roeck
2014-10-09 0:12 ` Mark Brown
2014-10-09 0:25 ` Guenter Roeck
2014-10-09 15:54 ` Mark Brown
2014-10-09 16:14 ` Guenter Roeck
2014-10-09 17:49 ` Guenter Roeck [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=20141009174958.GA4396@roeck-us.net \
--to=linux@roeck-us.net \
--cc=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--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 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.