From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ux500: Export SoC information and some platform clean-up
Date: Mon, 23 Jan 2012 15:58:53 +0000 [thread overview]
Message-ID: <201201231558.53673.arnd@arndb.de> (raw)
In-Reply-To: <1327165687-4223-1-git-send-email-lee.jones@linaro.org>
On Saturday 21 January 2012, Lee Jones wrote:
>
> This patch-set satisfies 4 objectives:
> 1. Ensures each platform device can specify a suitable parent
> 2. Provides a bus for SoC devices as a means to export information
> 3. Allows ux500 to make use of the new SoC bus
> 4. Cleans up unnecessary complexity from ux500 code
This version looks good to me, I have no further comments right now.
Greg, can you have another look? I think Lee has addressed all of
my comments as well as yours.
Linus, does this fit with your plans for migrating to only
device-tree based probing for ux500? I guess if this goes in
first, you will have to make a few changes so that it keeps working
when the devices are put into the dts.
Everyone else, who is planning to use the infrastructure besides ux500?
Arnd
next prev parent reply other threads:[~2012-01-23 15:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 17:08 [PATCH 0/6] ux500: Export SoC information and some platform clean-up Lee Jones
2012-01-21 17:08 ` [PATCH 1/6] mach-ux500: pass parent pointer to each platform device Lee Jones
2012-01-21 17:08 ` [PATCH 2/6] drivers/base: add bus for System-on-Chip devices Lee Jones
2012-01-28 1:05 ` Greg KH
2012-01-30 17:58 ` Arnd Bergmann
2012-01-30 18:34 ` Greg KH
2012-01-21 17:08 ` [PATCH 3/6] Documentation: add information for new sysfs soc bus functionality Lee Jones
2012-01-21 17:08 ` [PATCH 4/6] mach-ux500: export System-on-Chip information ux500 via sysfs Lee Jones
2012-01-21 17:08 ` [PATCH 5/6] mach-ux500: move top level platform devices in sysfs to /sys/devices/socX Lee Jones
2012-01-21 17:08 ` [PATCH 6/6] mach-ux500: remove intermediary add_platform_device* functions Lee Jones
2012-01-23 15:58 ` Arnd Bergmann [this message]
2012-01-23 16:03 ` [PATCH 0/6] ux500: Export SoC information and some platform clean-up Arnd Bergmann
2012-01-24 22:53 ` Linus Walleij
2012-01-25 15:01 ` Arnd Bergmann
2012-01-25 17:16 ` Lee Jones
2012-01-26 15:20 ` Arnd Bergmann
2012-01-27 0:56 ` Greg KH
2012-01-27 14:00 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2012-02-06 19:22 Lee Jones
2012-02-06 19:33 ` Linus Walleij
2012-02-10 19:43 ` Greg KH
2012-02-13 6:28 ` Arnd Bergmann
2012-02-13 19:54 ` Linus Walleij
2012-02-01 9:23 Lee Jones
2012-01-20 16:10 Lee Jones
2011-10-17 11:52 Lee Jones
2011-10-17 11:52 ` 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=201201231558.53673.arnd@arndb.de \
--to=arnd@arndb.de \
--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.