From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mfd: Fix runtime warning caused by duplicate device registration
Date: Thu, 5 Jul 2012 10:45:41 +0100 [thread overview]
Message-ID: <20120705094541.GK4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FF54406.3000307@linaro.org>
On Thu, Jul 05, 2012 at 08:36:38AM +0100, Lee Jones wrote:
> On 03/07/12 15:21, Mark Brown wrote:
> >This doesn't explain any of the issues, it just says that they exist.
> >My best guess would be that at least some of the issue is due to
> >instantiating the MFD cells from the device tree but it's hard to say
> >clearly.
> I'm guessing Arnd's email answered some of the questions you had.
> Let me know of you would like me to explain it in any greater
> detail.
No, frankly. It was just a general "why might we put things in DT"
answer which (especially given what you say below) isn't related to the
issue at all.
> By the way, this patch has nothing to do with registering these
> devices when DT is enabled. The code already does that. This is a
> bug fix, to stop multiple registration of the ab8500 when DT is
> _not_ enabled.
Really? It seems really surprising that adding more DT support to the
MFD core would have any bearing on something like this...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120705/1c4ded73/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@stericsson.com,
arnd@arndb.de, sameo@linux.intel.com
Subject: Re: [PATCH 1/1] mfd: Fix runtime warning caused by duplicate device registration
Date: Thu, 5 Jul 2012 10:45:41 +0100 [thread overview]
Message-ID: <20120705094541.GK4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FF54406.3000307@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Thu, Jul 05, 2012 at 08:36:38AM +0100, Lee Jones wrote:
> On 03/07/12 15:21, Mark Brown wrote:
> >This doesn't explain any of the issues, it just says that they exist.
> >My best guess would be that at least some of the issue is due to
> >instantiating the MFD cells from the device tree but it's hard to say
> >clearly.
> I'm guessing Arnd's email answered some of the questions you had.
> Let me know of you would like me to explain it in any greater
> detail.
No, frankly. It was just a general "why might we put things in DT"
answer which (especially given what you say below) isn't related to the
issue at all.
> By the way, this patch has nothing to do with registering these
> devices when DT is enabled. The code already does that. This is a
> bug fix, to stop multiple registration of the ab8500 when DT is
> _not_ enabled.
Really? It seems really surprising that adding more DT support to the
MFD core would have any bearing on something like this...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-05 9:45 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 11:59 [PATCH 1/1] mfd: Fix runtime warning caused by duplicate device registration Lee Jones
2012-07-03 11:59 ` Lee Jones
2012-07-03 12:35 ` Mark Brown
2012-07-03 12:35 ` Mark Brown
2012-07-03 13:07 ` Lee Jones
2012-07-03 13:07 ` Lee Jones
2012-07-03 13:24 ` Mark Brown
2012-07-03 13:24 ` Mark Brown
2012-07-03 13:48 ` Lee Jones
2012-07-03 13:48 ` Lee Jones
2012-07-03 14:21 ` Mark Brown
2012-07-03 14:21 ` Mark Brown
2012-07-05 7:36 ` Lee Jones
2012-07-05 7:36 ` Lee Jones
2012-07-05 9:45 ` Mark Brown [this message]
2012-07-05 9:45 ` Mark Brown
2012-07-05 11:46 ` Lee Jones
2012-07-05 11:46 ` Lee Jones
2012-07-05 12:06 ` Mark Brown
2012-07-05 12:06 ` Mark Brown
2012-07-05 12:15 ` Lee Jones
2012-07-05 12:15 ` Lee Jones
2012-07-05 12:29 ` Mark Brown
2012-07-05 12:29 ` Mark Brown
2012-07-05 12:41 ` Lee Jones
2012-07-05 12:41 ` Lee Jones
2012-07-05 12:45 ` Mark Brown
2012-07-05 12:45 ` Mark Brown
2012-07-05 12:55 ` Lee Jones
2012-07-05 12:55 ` Lee Jones
2012-07-05 13:03 ` Mark Brown
2012-07-05 13:03 ` Mark Brown
2012-07-05 13:12 ` Lee Jones
2012-07-05 13:12 ` Lee Jones
2012-07-05 13:20 ` Mark Brown
2012-07-05 13:20 ` Mark Brown
2012-07-05 13:54 ` Lee Jones
2012-07-05 13:54 ` Lee Jones
2012-07-05 13:57 ` Mark Brown
2012-07-05 13:57 ` Mark Brown
2012-07-05 14:06 ` Samuel Ortiz
2012-07-05 14:06 ` Samuel Ortiz
2012-07-05 13:57 ` Arnd Bergmann
2012-07-05 13:57 ` Arnd Bergmann
2012-07-05 14:04 ` Mark Brown
2012-07-05 14:04 ` Mark Brown
2012-07-05 14:06 ` Lee Jones
2012-07-05 14:06 ` Lee Jones
2012-07-05 14:13 ` Mark Brown
2012-07-05 14:13 ` Mark Brown
2012-07-05 14:35 ` Lee Jones
2012-07-05 14:35 ` Lee Jones
2012-07-05 15:41 ` Arnd Bergmann
2012-07-05 15:41 ` Arnd Bergmann
2012-07-05 15:51 ` Lee Jones
2012-07-05 15:51 ` Lee Jones
2012-07-03 14:01 ` Arnd Bergmann
2012-07-03 14:01 ` Arnd Bergmann
2012-07-03 14:43 ` Mark Brown
2012-07-03 14:43 ` Mark Brown
2012-07-05 7:33 ` Lee Jones
2012-07-05 7:33 ` Lee Jones
2012-07-05 13:08 ` Fabio Estevam
2012-07-05 13:08 ` Fabio Estevam
2012-07-05 13:13 ` Lee Jones
2012-07-05 13:13 ` Lee Jones
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=20120705094541.GK4111@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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.