From: Frank Rowand <frowand.list@gmail.com>
To: frowand.list@gmail.com
Cc: Rob Herring <robherring2@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Ivan T. Ivanov" <iivanov@mm-sol.com>,
Josh Cartwright <joshc@codeaurora.org>,
Courtney Cavin <courtney.cavin@sonymobile.com>,
Bjorn Andersson <bjorn@kryo.se>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 0/4] DT platform device name collision fixes
Date: Wed, 07 May 2014 19:54:30 -0700 [thread overview]
Message-ID: <536AF1E6.2010709@gmail.com> (raw)
In-Reply-To: <536AB91F.3010302@gmail.com>
On 5/7/2014 3:52 PM, Frank Rowand wrote:
> On 5/7/2014 2:48 PM, Rob Herring wrote:
>> From: Rob Herring <robh@kernel.org>
>>
>> This series fixes the device naming collisions that can occur with
>> nultiple devices having the same name and non-translatable unit
>> addresses. This issue was raised in this thread[1]. I intend to merge
>> this regardless of whether or not some hierarchy in sysfs is created.
>> That is really a separate issue independent of these fixes.
>>
>> I found and fix a couple of other issues in the process of testing the
>> fix.
>>
>> Rob
>>
>> [1] https://lkml.org/lkml/2014/4/23/312
>>
>> Rob Herring (4):
>> of/selftest: add testcase for nodes with same name and address
>> of/platform: return error on of_platform_device_create_pdata failure
>> of/platform: fix device naming for non-translatable addresses
>> of: kill off of_can_translate_address
>
> My opinion is that this approach is not a good approach to solving the
> problem. It is papering over a symptom, instead of dealing with the
> root cause.
>
> But despite my opinion, you can add to patches 2-4 (I did not test
> the self-test added in patch 1):
>
> Tested-by: frowand.list@gmail.com <frank.rowand@sonymobile.com>
>
> The patches resolve the name conflict originally reported for the
> qcomm PMIC, tested on 3.15-rc1, with a bunch of out of tree
> patches.
And you can add to the 4 patches:
Reviewed-by: Frank Rowand <frank.rowand@sonymobile.com>
-Frank
prev parent reply other threads:[~2014-05-08 2:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 21:48 [PATCH 0/4] DT platform device name collision fixes Rob Herring
2014-05-07 21:48 ` [PATCH 1/4] of/selftest: add testcase for nodes with same name and address Rob Herring
2014-05-08 2:51 ` Frank Rowand
2014-05-08 8:59 ` Grant Likely
2014-05-08 19:44 ` Frank Rowand
2014-05-09 4:28 ` Frank Rowand
2014-05-08 9:00 ` Grant Likely
2014-05-07 21:48 ` [PATCH 2/4] of/platform: return error on of_platform_device_create_pdata failure Rob Herring
2014-05-13 17:56 ` Olof Johansson
2014-05-13 18:31 ` Rob Herring
2014-05-13 20:32 ` Frank Rowand
2014-05-13 20:37 ` Olof Johansson
2014-05-14 7:43 ` Ivan T. Ivanov
2014-05-07 21:48 ` [PATCH 3/4] of/platform: fix device naming for non-translatable addresses Rob Herring
2014-05-08 10:41 ` Arnd Bergmann
2014-05-08 12:55 ` Rob Herring
2014-05-08 13:15 ` Arnd Bergmann
2014-05-08 11:47 ` Ivan T. Ivanov
2014-05-07 21:48 ` [PATCH 4/4] of: kill off of_can_translate_address Rob Herring
2014-05-07 22:52 ` [PATCH 0/4] DT platform device name collision fixes Frank Rowand
2014-05-08 2:54 ` Frank Rowand [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=536AF1E6.2010709@gmail.com \
--to=frowand.list@gmail.com \
--cc=bjorn@kryo.se \
--cc=courtney.cavin@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=iivanov@mm-sol.com \
--cc=joshc@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robherring2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox